From: Adam Jackson on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2722#note_1579470170
`=m`
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora
From: Adam Jackson on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2722#note_1579469992
`=m`
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora
From: Adam Jackson on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2487#note_1405790576
gpu ack
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
On Fri, 2018-09-14 at 18:35 -0600, Chris Murphy wrote:
> On Fri, Sep 14, 2018 at 5:22 PM, Chris Murphy wrote:
> > Hi,
> >
> > This looks intentional, as it's a lockdown related to Secure Boot, but
>
> Nope. The problem happens even with SB disabled. Happens with install
> media, and also as inst
On Thu, 2016-04-14 at 20:20 -0400, Josh Boyer wrote:
> Thanks for this. I'm going to let Peter weigh in on the ARM options.
> The rest look fine (lol KDBUS), but I'll verify a few tomorrow. Want
> to at least double check the I915 options.
Both DRM_I915_FBDEV and DRM_I915_KMS are gone as of 4.3
On Sun, 2015-11-22 at 16:49 -0600, Ian Pilcher wrote:
> I am hitting this pesign issue when trying to (locally) build a custom
> kernel RPM with mock:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1283475
>
> Is there any way to work around this before the pesign update makes it
> into stabl
On Mon, 2013-11-18 at 21:40 -0500, Josh Boyer wrote:
> Hi All,
>
> Every month I'm trying to publish a Fedora Kernel patch report that
> lists all of our patches and why we are carrying them. Thankfully,
> the past couple of times I've done this it's been pretty clear that
> for the most part we'
On Sun, 2013-03-03 at 07:18 -0500, Prarit Bhargava wrote:
> Do we need this anymore, or can it be dropped to something more reasonable
> like
> HZ=100 or HZ=250?
>
> Does anyone have an actual issue where they require HZ=1000?
I guess it depends what the implementation actually does. What does
On Wed, 2012-03-07 at 16:35 -0600, Bruno Wolff III wrote:
> I am getting syslog warnings sent out to my terminal sessions when
> IRQs get disabled. Is this really something severe enough to deserve
> that kind of notice? If so, should I be filing bugs?
>
> Sample message:
> Message from syslogd@wo
On Sat, 2011-12-17 at 08:08 -0600, Bruno Wolff III wrote:
> Does this affect the ability of hostile firewire devices to be able to
> access memory of a running system?
If you were hoping to use the IOMMU to protect you from hostile firewire
devices, then you'll need to turn it on explicitly now.
On Thu, 2010-06-24 at 11:32 -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 24, 2010 at 09:44:50AM -0400, Adam Jackson escreveu:
> > On Tue, 2010-06-22 at 17:37 -0700, Roland McGrath wrote:
> > > %package -n perf
> > > Summary: Performance monitoring for th
On Tue, 2010-06-22 at 17:37 -0700, Roland McGrath wrote:
> %package -n perf
> Summary: Performance monitoring for the Linux kernel
> Group: Development/System
> License: GPLv2
> +%if %{with_perftool}
> +Requires: kernel-perf(%{_arch}) >= %{version}-%{release}
> +%endif
Oughtn't this be:
Requ
On Tue, 2010-06-08 at 14:24 -0400, Linda Wang wrote:
> Dave Jones wrote:
> > I'm thinking we can probably drop some stuff from the spec.
> > Any thoughts on these ?
> >
> > - Some of the requires/conflicts are ancient, and kinda pointless to keep
> > around
> > (they reach back to rhl days)
> >
On Sat, 2010-04-17 at 12:36 +0200, drago01 wrote:
> This option seems to causes way to many issues, it is
> being investigated by Intel's chipset team for months now and
> we still don't have any outcome.
>
> The results so far are "black screen when starting X",
> "system hangs when using GL", "s
On Mon, 2010-04-12 at 17:36 +0200, Hans de Goede wrote:
> I'm currently looking into fixing:
> http://bugzilla.redhat.com/show_bug.cgi?id=565693
>
> The easiest way to do this would be to remove the always modprobe floppy
> code from anaconda and rely on udev for floppy driver loading.
Sigh, and
On Wed, 2010-03-31 at 16:43 -0400, Tom "spot" Callaway wrote:
> I'm of the opinion that we shouldn't be enabling "dead code" chunks at
> random, especially not in situations like this where the primary use is
> to encourage vendor utilization of closed source binary blobs or
> trusting a hardware
On Wed, 2010-03-31 at 16:40 -0400, Eric Paris wrote:
> Long ago we were ask to enable CONFIG_INTEL_TXT in the fedora kernels by
> a large user, the US National Security Agency:
>
> http://lists.fedoraproject.org/pipermail/kernel/2009-October/002228.html
>
> At the time the objection to this confi
17 matches
Mail list logo
