From: "Yu, Zhang" <yu.c.zhang@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, keir@xen.org, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, tim@xen.org,
ian.jackson@eu.citrix.com, donald.d.dugger@intel.com,
Xen-devel@lists.xen.org, Paul.Durrant@citrix.com,
zhiyuan.lv@intel.com, yang.z.zhang@intel.com
Subject: Re: [PATCH v6 0/2] add new p2m type class and new p2m type
Date: Tue, 09 Dec 2014 18:13:31 +0800 [thread overview]
Message-ID: <5486CB4B.5090801@linux.intel.com> (raw)
In-Reply-To: <5486C164020000780004DF97@mail.emea.novell.com>
On 12/9/2014 4:31 PM, Jan Beulich wrote:
>>>> On 09.12.14 at 03:02, <yu.c.zhang@linux.intel.com> wrote:
>> Thank you very much for your review.
>> And could you please also help me about how to get an ACK? I'm not
>> sure what's the next action I need to take. :-)
>
> I don't think you need to take any action at this point. The second
> patch will need Tim's ack, yes, but that's nothing to worry about
> (yet), since even with his ack the two patches wouldn't go in until
> after 4.5 got branched off of staging.
>
Got it, and thanks!
Yu
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>
next prev parent reply other threads:[~2014-12-09 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 3:55 [PATCH v6 0/2] add new p2m type class and new p2m type Yu Zhang
2014-12-06 3:55 ` [PATCH v6 1/2] add a new p2m type class - P2M_DISCARD_WRITE_TYPES Yu Zhang
2014-12-06 3:55 ` [PATCH v6 2/2] add a new p2m type - p2m_mmio_write_dm Yu Zhang
2014-12-08 16:20 ` Jan Beulich
2014-12-11 12:04 ` Tim Deegan
2014-12-11 13:23 ` Jan Beulich
2014-12-09 2:02 ` [PATCH v6 0/2] add new p2m type class and new p2m type Yu, Zhang
2014-12-09 8:31 ` Jan Beulich
2014-12-09 10:13 ` Yu, Zhang [this message]
2014-12-09 10:20 ` Tim Deegan
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=5486CB4B.5090801@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=Xen-devel@lists.xen.org \
--cc=donald.d.dugger@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=yang.z.zhang@intel.com \
--cc=zhiyuan.lv@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.