From: ebiederm@xmission.com (Eric W. Biederman)
To: michael@ellerman.id.au
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Greg KH <greg@kroah.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
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: Mon, 26 Mar 2007 05:52:26 -0600 [thread overview]
Message-ID: <m13b3s2pdx.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1174892991.4782.11.camel@concordia.ozlabs.ibm.com> (Michael Ellerman's message of "Mon, 26 Mar 2007 17:09:51 +1000")
Michael Ellerman <michael@ellerman.id.au> writes:
> OK. For starters, do you want to review the first eleven as I've sent
> them already, that saves spamming everyone again.
>
> If you're OK with those eleven, then I'll send the remaining 10 or so
> later in the week, broken up into (sort-of) functional groups.
Sounds like a decent plan. At a quick glance there is a reasonable chance
I'm going to run into issues with patch 9 or 10. Let me get as far as I can
with the acks and then we can see where we go with the next round of patches.
Eric
prev parent reply other threads:[~2007-03-26 11:53 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
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 [this message]
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=m13b3s2pdx.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=daniel.e.wolstenholme@intel.com \
--cc=davem@davemloft.net \
--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