From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Roger Pau Monne <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, Keir Fraser <keir@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] Config.mk: Update SEABIOS_UPSTREAM_TAG to 442502
Date: Thu, 14 Jan 2016 16:44:10 +0000 [thread overview]
Message-ID: <1452789850.32341.14.camel@citrix.com> (raw)
In-Reply-To: <1452782697.2185.39.camel@citrix.com>
On Thu, 2016-01-14 at 14:44 +0000, Ian Campbell wrote:
> On Thu, 2016-01-14 at 06:00 -0700, Jan Beulich wrote:
> > > > > On 14.01.16 at 12:32, <roger.pau@citrix.com> wrote:
> > > --- a/Config.mk
> > > +++ b/Config.mk
> > > @@ -255,9 +255,10 @@ MINIOS_UPSTREAM_REVISION ?=
> > > d25773c8afa2f4dbbb466116daeb60159ddd22bd
> > > # Thu Dec 3 11:23:25 2015 +0000
> > > # mini-os: Include libxentoollog with libxc
> > >
> > > -SEABIOS_UPSTREAM_REVISION ?= rel-1.9.0
> > > -# Tue Nov 17 09:18:44 2015 -0500
> > > -# docs: Note v1.9.0 release
> > > +SEABIOS_UPSTREAM_REVISION ?=
> > > 44250252eeaefd5e81bae2f73639bd323682217b
> > > +# Thu Jan 7 12:02:51 2016 -0500
> > > +# tpm: Do not set TPM in failure mode if menu command fails
> > > +# NB: we should try to update to a rel-* version before releasing
> > > Xen.
> >
> > Assuming they cut a 1.9.1 by then including that fix, won't we risk
> > moving backwards in that case? Wouldn't it be better in such a
> > situation to follow the ipxe model and apply patches on top of the
> > most recent release?
>
> Good point.
>
> I shall drop seabios-devel a line re 1.9.1 or 1.10.0 and see what's what.
In response to my line there is now 1.9-stable branch in seabios.git, which
contains just the patch of interest. I propose we update to that branch, as
below (+ appropriate pushes to our seabios.git tree to make the branch
appear there).
Ian.
commit a661f70a8aad3fe7b2c828632714785a04b1d96b
Author: Ian Campbell <ian.campbell@citrix.com>
Date: Thu Jan 14 16:43:42 2016 +0000
SEABIOS_UPSTREAM_REVISION Update
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
diff --git a/Config.mk b/Config.mk
index 62f8209..d654af8 100644
--- a/Config.mk
+++ b/Config.mk
@@ -255,9 +255,9 @@ MINIOS_UPSTREAM_REVISION ?= d25773c8afa2f4dbbb466116daeb60159ddd22bd
# Thu Dec 3 11:23:25 2015 +0000
# mini-os: Include libxentoollog with libxc
-SEABIOS_UPSTREAM_REVISION ?= rel-1.9.0
-# Tue Nov 17 09:18:44 2015 -0500
-# docs: Note v1.9.0 release
+SEABIOS_UPSTREAM_REVISION ?= 3403ac4313812752be6e6aac35239ca6888a8cab
+# Mon Dec 28 13:50:41 2015 +0100
+# build: fix typo in buildversion.py
ETHERBOOT_NICS ?= rtl8139 8086100e
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-14 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 11:32 [PATCH] Config.mk: Update SEABIOS_UPSTREAM_TAG to 442502 Roger Pau Monne
2016-01-14 13:00 ` Jan Beulich
2016-01-14 14:44 ` Ian Campbell
2016-01-14 16:44 ` Ian Campbell [this message]
2016-01-14 16:56 ` Roger Pau Monné
2016-01-14 17:01 ` Ian Campbell
2016-01-15 10:56 ` Ian Campbell
2016-01-14 16:57 ` Roger Pau Monné
2016-01-14 16:57 ` Jan Beulich
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=1452789850.32341.14.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=roger.pau@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.