qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: mdroth <mdroth@linux.vnet.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-1.5?] ide-test: Fix endianness problems
Date: Wed, 15 May 2013 11:07:40 -0500	[thread overview]
Message-ID: <20130515160740.GA23880@vm> (raw)
In-Reply-To: <8761ykdzjs.fsf@codemonkey.ws>

On Wed, May 15, 2013 at 10:37:43AM -0500, Anthony Liguori wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
> 
> > Il 15/05/2013 15:24, Kevin Wolf ha scritto:
> >> Am 15.05.2013 um 15:15 hat Paolo Bonzini geschrieben:
> >>> Il 15/05/2013 15:00, Kevin Wolf ha scritto:
> >>>> The test case passes on big endian hosts now (tested on ppc64)
> >>>>
> >>>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> >>>
> >>> For 1.5?  Do we need an extra -rc?
> >> 
> >> An extra -rc for a test case fix on big endian hosts is probably too
> >> much... But if it can still be applied for the release, sure, why not.
> >
> > Well, we have Mac OS X not building,
> 
> Peter's patch fixes it and will be in -rc2
> 
> > BSDs not supporting the GTK+
> 
> We don't have a formal support statement, but I don't think it's
> controversial to say that BSD hosts are a secondary platform from a host
> point of view.
> 
> A build issue in an optional feature on a secondary platform is not
> something I'd consider a release blocker.
> 
> > release, and SLIRP broken on Windows.
> 
> This is a tough one since it's the default networking backend.  That
> said, it likely has been broken for a while (months) and no one
> noticed.  That makes me think that fixing in stable (particularly if we
> scheduled a stable release for two weeks after 1.5.0) is reasonable.

This is a bit tight. Freeze for 1.4.2 is the same day as 1.5.0, so we'd
be testing 2 stable releases at the same time.

So if we do this, I think it we should restrict it to fixing the specific
issues we're considering as potential 1.5.0 release blockers so we can
focus on those in testing rather than opening it up for general fixes.

> 
> Regards,
> 
> Anthony Liguori
> 
> >  At least the first two have
> > patches on the list, the last is bisected but no patch yet.
> >
> > Paolo
> 

  reply	other threads:[~2013-05-15 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 13:00 [Qemu-devel] [PATCH] ide-test: Fix endianness problems Kevin Wolf
2013-05-15 13:15 ` [Qemu-devel] [PATCH for-1.5?] " Paolo Bonzini
2013-05-15 13:24   ` Kevin Wolf
2013-05-15 13:47     ` Paolo Bonzini
2013-05-15 15:37       ` Anthony Liguori
2013-05-15 16:07         ` mdroth [this message]
2013-05-16  9:04 ` [Qemu-devel] [PATCH] " Stefan Hajnoczi
2013-05-16  9:12   ` Kevin Wolf
2013-05-16 12:50 ` Anthony Liguori

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=20130515160740.GA23880@vm \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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).