linux-kernel - Re: [PATCH 0/21] MSI rework

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:	Thu, 22 Mar 2007 15:08:37 -0700
From:	Greg KH <greg@...ah.com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Michael Ellerman <michael@...erman.id.au>,
	linux-pci@...ey.karlin.mff.cuni.cz,
	"David S. Miller" <davem@...emloft.net>,
	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>,
	daniel.e.wolstenholme@...el.com
Subject: Re: [PATCH 0/21] MSI rework

On Fri, Mar 23, 2007 at 09:02:16AM +1100, Benjamin Herrenschmidt wrote:
> > > i.e.  First the simple bug fixes that should purely be restructure of
> > > msi.c with no affect on anything outside of it.
> > > 
> > > And then get into the architecture enhancements.
> > 
> > I agree, care to break these down into a smaller series of patches that
> > can go into -mm for testing?
> 
> I don't see the point in breaking the serie... you can bisect half way
> through if necessary... it's made of small patches that are done, afaik,
> in such a way that the whole thing should still work at any level in the
> serie.
> 
> The serie just expresses the dependency between them.

Ok, then which patches in the series should be acceptable to take right
now for 2.6.22?  The "clean up the BUG" ones?

thanks,

greg k-h
-
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/