qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Marc Hartmayer <mhartmay@linux.ibm.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PULL 0/2] Fix for the s390-ccw bios
Date: Fri, 29 Nov 2019 12:43:05 +0000	[thread overview]
Message-ID: <CAFEAcA-g9HNCx_4XSeSLgmOQeq0FxZOp5LRKwnmTkgKH3g1tVg@mail.gmail.com> (raw)
In-Reply-To: <f5203ce4-6684-42f5-8cf2-c5e2a54b5947@redhat.com>

On Fri, 29 Nov 2019 at 12:08, Thomas Huth <thuth@redhat.com> wrote:
> without the fix, certain boot scenarios break:
>
> - "-boot menu=on" does not work anymore.
>
> - It's not possible anymore to specify the s390x-specific "loadparm"
>   option (can be used e.g. with "-machine s390-ccw-virtio,loadparm=xyz")
>   This is e.g. important for booting alternate kernel that are installed
>   on the guest's hard disk image.
>
> The fix is just a one-liner, has been reviewed and tested by multiple
> people already, so it should not cause any other regressions.

OK, that sounds worth fixing.

> I think you could merge it also without doing another RC next week

I never do releases which have any changes which haven't been in
an RC. This is a rule I'm not willing to break. Sometimes we do
an RC with less than the usual week's delay if there's just one
last simple bug to be fixed.

thanks
-- PMM


  reply	other threads:[~2019-11-29 13:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 10:08 [PULL 0/2] Fix for the s390-ccw bios Thomas Huth
2019-11-29 10:08 ` [PULL 1/2] pc-bios/s390-ccw: fix sclp_get_loadparm_ascii Thomas Huth
2019-11-29 10:08 ` [PULL 2/2] pc-bios/s390: Update firmware image with the "fix sclp_get_loadparm_ascii" patch Thomas Huth
2019-11-29 10:46 ` [PULL 0/2] Fix for the s390-ccw bios Peter Maydell
2019-11-29 12:07   ` Thomas Huth
2019-11-29 12:43     ` Peter Maydell [this message]
2019-11-29 15:44 ` Peter Maydell

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=CAFEAcA-g9HNCx_4XSeSLgmOQeq0FxZOp5LRKwnmTkgKH3g1tVg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=mhartmay@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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).