linux-kernel - Re: 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]

Message-ID: <463688AD.1050903@garzik.org>
Date:	Mon, 30 Apr 2007 20:24:13 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: to something appropriate (was Re: 2.6.22 -mm merge plans)

Andrew Morton wrote:
> Yeah, a new-id patch is a pretty critical bugfix if you happen to have that
> hardware.  I'll get all these into 2.6.22 by whatever means and will adopt
> your advice in future.
> 
> Probably these should go into -stable too, but I don't know what
> Greg&Chris's position is on new device IDs.

I don't know either.  But a one-line ID patch is pretty painless 
considering the gain, so I would vote for stable@...nel.org taking such 
patches.

If it's more than one line added per ID though, NAK for -stable, IMO...

	Jeff


-
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/