From: Wei Liu <wei.liu2@citrix.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: ian.jackson@eu.citrix.com, Wei Liu <wei.liu2@citrix.com>,
ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH V3 2/5] Config.mk: update OVMF changeset
Date: Tue, 29 Oct 2013 14:21:38 +0000 [thread overview]
Message-ID: <20131029142138.GH5221@zion.uk.xensource.com> (raw)
In-Reply-To: <526FC331.1030502@m2r.biz>
On Tue, Oct 29, 2013 at 03:16:17PM +0100, Fabio Fantoni wrote:
> Il 29/10/2013 12:39, Wei Liu ha scritto:
> >Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> >---
> > Config.mk | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/Config.mk b/Config.mk
> >index 1879454..dad2dc4 100644
> >--- a/Config.mk
> >+++ b/Config.mk
> >@@ -232,7 +232,7 @@ OVMF_UPSTREAM_URL ?= git://xenbits.xen.org/ovmf.git
> > QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
> > SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
> > endif
> >-OVMF_UPSTREAM_REVISION ?= b0855f925c6e2e0b21fbb03fab4b5fb5b6876871
> >+OVMF_UPSTREAM_REVISION ?= a93b0e3f6895a074b99c8817181dfa6dbc7a4807
> > QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
> > SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
> > # Fri Aug 2 14:12:09 2013 -0400
>
> This patch update only the ovmf changeset but not the repository,
> now git://xenbits.xen.org/ovmf.git is not updated, so you have to
> update it or change also repository to
> git://xenbits.xen.org/people/liuw/ovmf.git.
> All other things look good to me, now I test this series of patches.
I don't have the permission to push to that repository so I need to
defer this to maintainers.
Again, you can probably wait until this series go through push gate
before conducting any test.
Wei.
next prev parent reply other threads:[~2013-10-29 14:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 11:39 [PATCH V3 0/5] Reintroduce OVMF support Wei Liu
2013-10-29 11:39 ` [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048 Wei Liu
2013-11-01 11:14 ` George Dunlap
2013-11-01 16:02 ` Ian Campbell
2013-11-01 16:10 ` Wei Liu
2013-11-01 16:23 ` Ian Campbell
2013-11-06 10:32 ` Wei Liu
2013-11-06 10:41 ` Ian Campbell
2013-11-06 18:04 ` Stefano Stabellini
2013-11-07 11:03 ` Ian Campbell
2013-11-07 11:15 ` Processed: " xen
2013-11-06 12:04 ` Wei Liu
2013-10-29 11:39 ` [PATCH V3 2/5] Config.mk: update OVMF changeset Wei Liu
2013-10-29 14:16 ` Fabio Fantoni
2013-10-29 14:21 ` Wei Liu [this message]
2013-10-29 16:15 ` Fabio Fantoni
2013-10-29 16:34 ` Wei Liu
2013-10-30 11:33 ` Fabio Fantoni
2013-10-30 11:50 ` Wei Liu
2013-10-30 12:57 ` Fabio Fantoni
2013-10-30 14:05 ` Wei Liu
2013-10-30 15:52 ` Fabio Fantoni
2013-10-30 15:58 ` Wei Liu
2013-10-31 9:47 ` Fabio Fantoni
2013-10-31 10:03 ` Wei Liu
2013-10-31 11:22 ` Fabio Fantoni
2013-10-31 14:40 ` Wei Liu
2013-10-31 15:41 ` Fabio Fantoni
2013-10-30 12:09 ` Wei Liu
2013-10-30 12:42 ` Fabio Fantoni
2013-11-01 16:05 ` Ian Campbell
2013-10-29 11:39 ` [PATCH V3 3/5] tools: clone ovmf to ovmf-dir directory Wei Liu
2013-10-29 11:39 ` [PATCH V3 4/5] tools: support system supplied ovmf binary Wei Liu
2013-10-29 11:39 ` [PATCH V3 5/5] tools: Enable OVMF build by default Wei Liu
2013-11-11 14:09 ` [PATCH V3 0/5] Reintroduce OVMF support Ian Campbell
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=20131029142138.GH5221@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=fabio.fantoni@m2r.biz \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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).