From: annie li <annie.li@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jeremy@goop.org" <jeremy@goop.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Kurt Hackel <Kurt.Hackel@oracle.com>
Subject: Re: Forth version patches for upstreaming grant table version 2
Date: Wed, 23 Nov 2011 08:46:07 +0800 [thread overview]
Message-ID: <4ECC424F.6070009@oracle.com> (raw)
In-Reply-To: <20111122143220.GB3430@phenom.dumpdata.com>
On 2011-11-22 22:32, Konrad Rzeszutek Wilk wrote:
> On Tue, Nov 22, 2011 at 06:21:47PM +0800, ANNIE LI wrote:
>
>> Hi
>>
>> The following patches introduce and implement grant table version 2.
>> This is the forth version patches, and based on v3.2.0-rc1+. Changes
>> from the previous patches are following:
>>
>> * Fix an indentation issue of the code.
>>
>
> I've put your patches in my queue for 3.3. They should show up in my #linux-next
> tonight if there are no outstanding compile/test issues.
>
Thanks, Konrad.
Tons of thanks to you guys for your reviewing on these patches, the
patches were improved so much with your helps.
Thanks
Annie
prev parent reply other threads:[~2011-11-23 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 10:21 Forth version patches for upstreaming grant table version 2 ANNIE LI
2011-11-22 10:25 ` [PATCH 1/4] xen/granttable: Introducing grant table V2 stucture annie.li
2011-11-22 10:26 ` [PATCH 2/4] xen/granttable: Refactor some code annie.li
2011-11-22 10:27 ` [PATCH 3/4] xen/granttable: Grant tables V2 implementation annie.li
2011-11-22 10:27 ` [PATCH 4/4] xen/granttable: Keep code format clean annie.li
2011-11-22 14:32 ` Forth version patches for upstreaming grant table version 2 Konrad Rzeszutek Wilk
2011-11-23 0:46 ` annie li [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=4ECC424F.6070009@oracle.com \
--to=annie.li@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Kurt.Hackel@oracle.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).