Mailinglist Archive: opensuse-kernel (81 mails)
| < Previous | Next > |
Re: [opensuse-kernel] opensuse 11.0 kernel patch justification needed from you
- From: Greg KH <gregkh@xxxxxxx>
- Date: Thu, 7 Feb 2008 20:31:48 -0800
- Message-id: <20080208043148.GI9456@xxxxxxx>
On Wed, Feb 06, 2008 at 09:42:22AM +0100, Andi Kleen wrote:
Ok, will we know when those changes get merged so we no longer have to
take this patch?
Ok.
Try poking them again if you get the chance.
Not yet, I hadn't. I see that there now.
Ok, just wanted to make sure.
Ok, will move over to Xen directory then.
Yeah, should save us on support calls.
I'll try to push it.
But there already is a twofish crypto module in the upstream kernel.
Why are we adding another one? Shouldn't we use the one already there?
If there are problems with the upstream one, we should fix it, not just
drag in another new implementation.
thanks,
greg k-h
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx
On Tuesday 05 February 2008 23:10:07 Greg KH wrote:
If these defaults are too small, why haven't we got upstream to take
the change?:
patches.suse/shmall-bigger
There is a change being worked on upstream (or rather mm) to do this more
generically.
Ok, will we know when those changes get merged so we no longer have to
take this patch?
Andi Kleen:
Why aren't these upstream?
patches.arch/disable-apic-error
The idea was that we should find out upstream why the APIC error occurs
and so not silence it, but don't do that for the distro production kernels.
Ok.
patches.arch/x86-nvidia-timer-quirk
Hmm, I thought I had submitted that one but it seems to have gotten lost
somewhere.
patches.suse/wireless-no-aes-select
I submitted that one. The maintainers thought it was not needed, but I'm
still not convinced. Right now modprobe aes without this patch still
does load the wrong code I think.
Try poking them again if you get the chance.
Bernhard Kaindl:
Why are these patches not upstream:
patches.drivers/early-firewire.diff
They are. Did you not check mainline?
Not yet, I hadn't. I see that there now.
KBD fun:
KDB
These might go upstream, but I really doubt it. Note that kgdb hooks
might be in mainline soon,
No, the basic hooks have been in forever. kgdb adds a few new one,
but most of them are actually misguided and KDB typically doesn't need them.
so these might need to be majorly rewritten
to handle these hooks. For now we'll keep them, but I really doubt
their usability. Does anyone use this?
It is the current standard kernel debugger for SUSE and afaik
used by a lot of people.
Ok, just wanted to make sure.
patches.fixes/ipv6-no-autoconf
Might be still needed for Xen
Ok, will move over to Xen directory then.
patches.fixes/oom-warning
This patch seems valuable to me.
Yeah, should save us on support calls.
patches.fixes/tiocgdev
This is needed for init. There is unfortunately some philosophical
disagreement on that one for mainline (I tried to submit it a long time ago).
Maintainer is Werner Fink.
Probably would make sense to resubmit it -- i'm a little tired of
always seeing the "kernel does not support TIOCGDEV" messages
when I boot a mainline kernel.
I'll try to push it.
patches.suse/crasher-26.diff
This one is a valuable debugging tool and should be probably
submitted.
patches.suse/twofish-2.6 (We gotta be able to drop this one
now, right? If not, why isn't it
upstream?)
No we can't because that would break updates with encrypted file systems.
But there already is a twofish crypto module in the upstream kernel.
Why are we adding another one? Shouldn't we use the one already there?
If there are problems with the upstream one, we should fix it, not just
drag in another new implementation.
thanks,
greg k-h
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx
| < Previous | Next > |