Xen-Devel Archive on lore.kernel.org
 help / color / Atom feed
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
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.


Anthony PERARD

Xen-devel mailing list

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 16:10 [Xen-devel] " 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 publically 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:

* 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 \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Xen-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/xen-devel/0 xen-devel/git/0.git
	git clone --mirror https://lore.kernel.org/xen-devel/1 xen-devel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 xen-devel xen-devel/ https://lore.kernel.org/xen-devel \
		xen-devel@lists.xenproject.org xen-devel@archiver.kernel.org
	public-inbox-index xen-devel

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox