linux-kernel - Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 1 May 2007 17:40:33 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Chuck Ebbert <cebbert@...hat.com>
Cc:	Greg KH <greg@...ah.com>, Jeff Garzik <jeff@...zik.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge
 plans)

> > But distros can easily add the device id to their kernel if needed, it
> > isn't something that the -stable tree shoud be accepting.  Otherwise, we
> > will be swamped with those types of patches...
> > 
> 
> Oh sure, leave the distros swamped with them instead. :)
> 
> And they all have to do it separately, meaning they don't stay in sync
> and they duplicate each other's work...

Well they *don't* have to work that separately. They could set up some
shared tree which would look suspiciously like what Greg is doing but
with the ID updates.... ;)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/