All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: George Dunlap <george.dunlap@eu.citrix.com>,
	Sander Eikelenboom <linux@eikelenboom.it>,
	Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Update seabios and upstream qemu versions used on xen-unstable
Date: Tue, 15 Apr 2014 16:33:22 +0200	[thread overview]
Message-ID: <534D4332.1090206@m2r.biz> (raw)
In-Reply-To: <534D32FF.7020308@eu.citrix.com>

Il 15/04/2014 15:24, George Dunlap ha scritto:
> On 04/15/2014 12:51 PM, Sander Eikelenboom wrote:
>>
>> Tuesday, April 15, 2014, 1:18:32 PM, you wrote:
>>
>>> On Mon, Apr 14, 2014 at 01:11:36PM +0200, Fabio Fantoni wrote:
>>>> I think it would be good to update seabios and upstream qemu 
>>>> versions used
>>>> with xen-unstable.
>>>> Recently I tested on my testing system with xen-unstable seabios 
>>>> updated to
>>>> debian package version 1.7.4-4 without finding regressions and 
>>>> upstream qemu
>>>> 2.0-rc0 from git where I found 2 regressions already reported and 
>>>> solved on
>>>> upstream git.
>>>> I updated qemu to 2.0-rc2 where I did some tests without finding other
>>>> regressions or bugs for now.
>>>> I also noticed on the wiki page of the next hackathon the topic 
>>>> "QEMU and
>>>> SeaBIOS regression testing". As I reported some time ago it would 
>>>> be of
>>>> great help.
>>
>>> I was thinking of submitting the update for QEMU when QEMU 2.0 will be
>>> out.
>>
>> Wouldn't it be sensible for xen-unstable to follow at least the qemu 
>> rc's so those
>> get build and tested in the osstests ?
>
> It might make more sense to have a osstest target that used vanilla 
> upstream -- in fact, there may be one already.
>
>  -George

Yes is the vanilla upstream test that is missing, at least testing each 
stable version from rc0 can be a start but test daily or weekly git 
master would be perfect.
Now only upstream qemu of xen git is tested but is old of some upstream 
versions ago and the merging with newer versions for now were always 
after a long time out of the stable upstream version :(

  parent reply	other threads:[~2014-04-15 14:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 11:11 Update seabios and upstream qemu versions used on xen-unstable Fabio Fantoni
2014-04-14 11:19 ` Sander Eikelenboom
2014-04-15 11:18 ` Anthony PERARD
2014-04-15 11:51   ` Sander Eikelenboom
2014-04-15 13:24     ` George Dunlap
2014-04-15 14:03       ` Sander Eikelenboom
2014-04-15 14:33       ` Fabio Fantoni [this message]
2014-04-15 17:59         ` Konrad Rzeszutek Wilk
2014-04-15 19:41           ` Fabio Fantoni
2014-04-16  9:33             ` Wei Liu
2014-04-16 10:04               ` Ian Campbell
2014-04-16 11:22                 ` Fabio Fantoni
2014-04-16 12:14                   ` Ian Campbell
2014-04-16 14:04                     ` Fabio Fantoni
2014-04-16 14:10                       ` Ian Campbell
2014-04-17 16:14                         ` Ian Jackson
2014-04-17 16:28                           ` 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=534D4332.1090206@m2r.biz \
    --to=fabio.fantoni@m2r.biz \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xensource.com \
    /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.