From: Anthony PERARD <anthony.perard@citrix.com>
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>,
"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 16:57:08 +0100 [thread overview]
Message-ID: <20190701155708.GL13449@perard.uk.xensource.com> (raw)
In-Reply-To: <e65a329b-03e3-1beb-d91a-2724b9098fe9@suse.com>
On Mon, Jul 01, 2019 at 03:19:29PM +0000, Jan Beulich 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?
Well, the file Config.mk is maintained by THE REST, but the ovmf tree is
maintained by Wei and me. So, we can wait for Wei to put his ack, or
just have one of THE REST maintainer put a ack would be enough I think.
As for a policy for such updates, they often seems to go in without any
acks. Recent updates of mini-os, qemu-trad, seabios don't have acks.
It's the same for qemu-xen, but that tree is gated by osstest.
Thanks,
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-07-01 15:57 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 [this message]
2019-07-01 22:04 ` Wei Liu
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=20190701155708.GL13449@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@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=wl@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).