From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH] Config.mk: update OVMF changeset
Date: Sun, 8 Dec 2013 20:50:20 +0000 [thread overview]
Message-ID: <1386535820-13360-1-git-send-email-wei.liu2@citrix.com> (raw)
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>
---
To IanC,
OVMF tree can be found at:
http://xenbits.xen.org/git-http/people/liuw/ovmf.git for-xenbits
Please push that branch to Xenbits.
I presume that
tools: enable OVMF build for Linux by default
is in your queue so I don't bother resending that. This patch should
probably go before that one.
To George,
Good: users can get their hands dirty with OVMF.
Bad : if somebody spots a problem in interface we have to live with it.
But, if nobody gets a chance to use it then nobody can spot a problem.
We've merged the interface in tree. I think the advantage of having OVMF
for 4.4 outweights the disadvantage. I suggest we let OVMF go in and
mark it as experimental.
---
Config.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Config.mk b/Config.mk
index 7eeed31..9b5d1bd 100644
--- a/Config.mk
+++ b/Config.mk
@@ -233,7 +233,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 ?= a93b0e3f6895a074b99c8817181dfa6dbc7a4807
+OVMF_UPSTREAM_REVISION ?= 447d264115c476142f884af0be287622cd244423
QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
SEABIOS_UPSTREAM_TAG ?= rel-1.7.3.1
# Fri Aug 2 14:12:09 2013 -0400
--
1.7.10.4
next reply other threads:[~2013-12-08 20:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 20:50 Wei Liu [this message]
2013-12-09 11:04 ` [PATCH] Config.mk: update OVMF changeset George Dunlap
2013-12-09 11:10 ` Wei Liu
2013-12-09 11:17 ` George Dunlap
2013-12-09 11:33 ` Ian Campbell
2013-12-09 15:46 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2015-10-14 11:41 Wei Liu
2015-10-22 15:55 ` Ian Campbell
2015-10-22 15:58 ` Ian Jackson
2015-10-22 16:02 ` Wei Liu
2015-10-22 16:09 ` Ian Campbell
2015-10-22 16:11 ` Stefano Stabellini
2015-10-22 17:08 ` Ian Jackson
2015-10-23 8:01 ` Jan Beulich
2015-10-23 9:11 ` Ian Campbell
2015-10-23 10:08 ` Stefano Stabellini
2015-10-23 11:18 ` Ian Jackson
2015-10-23 11:38 ` Stefano Stabellini
2015-10-23 11:56 ` Ian Jackson
2015-10-23 11:52 ` Jan Beulich
2015-10-23 12:16 ` Ian Campbell
2015-10-23 12:43 ` Stefano Stabellini
2015-10-23 12:56 ` Ian Campbell
2015-10-23 13:16 ` Fabio Fantoni
2015-10-23 13:38 ` Ian Campbell
2015-11-12 10:06 Wei Liu
2015-11-16 12:08 ` Ian Campbell
2015-11-16 12:10 ` Wei Liu
2017-03-23 17:10 Anthony PERARD
2017-09-22 17:20 Anthony PERARD
2017-09-25 7:31 ` Jan Beulich
2017-09-25 14:20 ` Dario Faggioli
2018-07-25 14:38 Anthony PERARD
2020-08-12 9:55 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=1386535820-13360-1-git-send-email-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.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).