From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Michael Ellerman <michael@ellerman.id.au>,
linux-pci@atrey.karlin.mff.cuni.cz,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
daniel.e.wolstenholme@intel.com
Subject: Re: [PATCH 0/21] MSI rework
Date: Fri, 23 Mar 2007 09:02:16 +1100 [thread overview]
Message-ID: <1174600936.10836.53.camel@localhost.localdomain> (raw)
In-Reply-To: <20070322190834.GA14802@kroah.com>
> > 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.
Ben.
next prev parent reply other threads:[~2007-03-22 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1174560686.307511.956605711793.qpush@cradle>
2007-03-22 15:01 ` [PATCH 0/21] MSI rework Eric W. Biederman
2007-03-22 19:08 ` Greg KH
2007-03-22 22:02 ` Benjamin Herrenschmidt [this message]
2007-03-22 22:08 ` Greg KH
2007-03-22 22:31 ` Benjamin Herrenschmidt
2007-03-23 4:17 ` Michael Ellerman
2007-03-23 10:25 ` Eric W. Biederman
2007-03-26 7:09 ` Michael Ellerman
2007-03-26 11:52 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1174600936.10836.53.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=daniel.e.wolstenholme@intel.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=michael@ellerman.id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox