From: Jan Beulich <jbeulich@suse.com>
To: pdurrant@amazon.com, andrew.cooper3@citrix.com
Cc: xen-devel@lists.xenproject.org
Subject: Re: [ANNOUNCE] Xen 4.14 Development Update
Date: Fri, 17 Apr 2020 11:38:25 +0200 [thread overview]
Message-ID: <15ddf257-adb3-9384-0b38-d5ecd568746b@suse.com> (raw)
In-Reply-To: <20200417091057.136-1-paul@xen.org>
On 17.04.2020 11:10, Paul Durrant wrote:
> * Memory read caching in emulation (v5)
> - Jan Beulich
I'd like to take this as an opportunity to ask on the disposition
of this series: Under the new rules in principle I could have put
this in with Paul's R-b, but given the prior discussions I didn't
want to do so without at least an informal okay from you, Andrew.
Now that the sending of v5 as well as Paul's reviewing of it is 6
weeks back, I guess unless I hear otherwise pretty soon I'm going
to commit the remaining 3 patches some time next week.
Jan
next prev parent reply other threads:[~2020-04-17 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 9:10 [ANNOUNCE] Xen 4.14 Development Update Paul Durrant
2020-04-17 9:38 ` Jan Beulich [this message]
2020-04-24 7:38 Paul Durrant
2020-04-24 7:55 ` Jan Beulich
2020-04-24 7:59 ` Durrant, Paul
2020-04-24 15:54 ` Tamas K Lengyel
2020-04-24 16:00 ` Durrant, Paul
2020-04-29 13:22 ` Jason Andryuk
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=15ddf257-adb3-9384-0b38-d5ecd568746b@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=pdurrant@amazon.com \
--cc=xen-devel@lists.xenproject.org \
/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).