From: Wei Liu <wl@xen.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
KonradRzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Anthony PERARD <anthony.perard@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Ping: [PATCH] Config.mk: update OVMF to edk2-stable201905
Date: Mon, 1 Jul 2019 23:04:34 +0100 [thread overview]
Message-ID: <CAK9nU=rhyKdFBm96MGAVZhJuBXeVSDxU5w_4tvQh-G7wNKr7rQ@mail.gmail.com> (raw)
In-Reply-To: <e65a329b-03e3-1beb-d91a-2724b9098fe9@suse.com>
On Mon, 1 Jul 2019 at 16:22, Jan Beulich <JBeulich@suse.com> wrote:
>
> On 01.07.2019 17:04, Anthony PERARD wrote:
> > On Mon, Jun 17, 2019 at 05:10:50PM +0100, Anthony PERARD wrote:
> >> Update to the latest stable tag.
> >>
> >> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> >
> > Could one of you commit this patch?
>
> I was wondering what the policy here is - do such updates go in
> without any acks?
>
Anthony is the maintainer. I think his judgement is sufficient.
Previously I just committed his patch without giving my ack.
If you really want one:
Acked-by: Wei Liu <wl@xen.org>
Wei.
> Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-07-01 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 16:10 [Xen-devel] [PATCH] Config.mk: update OVMF to edk2-stable201905 Anthony PERARD
2019-07-01 15:04 ` [Xen-devel] Ping: " Anthony PERARD
2019-07-01 15:19 ` Jan Beulich
2019-07-01 15:57 ` Anthony PERARD
2019-07-01 22:04 ` Wei Liu [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='CAK9nU=rhyKdFBm96MGAVZhJuBXeVSDxU5w_4tvQh-G7wNKr7rQ@mail.gmail.com' \
--to=wl@xen.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--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).