From: Peter Maydell <peter.maydell@linaro.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Cornelia Huck <cohuck@redhat.com>, Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PULL 0/2] s390x: Fixes for 2.12
Date: Fri, 23 Mar 2018 11:22:40 +0000 [thread overview]
Message-ID: <CAFEAcA9Q-DKtH6UKH3R=er19jqxQRERGqLWogSL0YegdOTt6VA@mail.gmail.com> (raw)
In-Reply-To: <20180323091441.116971-1-borntraeger@de.ibm.com>
On 23 March 2018 at 09:14, Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Peter,
>
> 2 fixes for 2.12. Please pull
>
> The following changes since commit d522e0bd18364f6d784d43edab35b0563d21f6f3:
>
> gitmodules: Use the QEMU mirror of qemu-palcode (2018-03-22 19:24:16 +0000)
>
> are available in the Git repository at:
>
> git://github.com/borntraeger/qemu.git tags/s390x-20180323
>
> for you to fetch changes up to 06a97edac172f52971d7bdca6bb56a1edcb1b8f6:
>
> s390x/cpumodel: fix feature groups and breakage of MSA8 (2018-03-23 09:05:42 +0000)
>
> ----------------------------------------------------------------
> s390x: Fixes for 2.12
>
> - Fix for the s390 cpumodel
> - Forbid multifunction PCI devices
>
> ----------------------------------------------------------------
Applied, thanks.
-- PMM
prev parent reply other threads:[~2018-03-23 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 9:14 [Qemu-devel] [PULL 0/2] s390x: Fixes for 2.12 Christian Borntraeger
2018-03-23 9:14 ` [Qemu-devel] [PULL 1/2] s390x/pci: forbid multifunction pci device Christian Borntraeger
2018-03-23 9:14 ` [Qemu-devel] [PULL 2/2] s390x/cpumodel: fix feature groups and breakage of MSA8 Christian Borntraeger
2018-03-23 11:22 ` Peter Maydell [this message]
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='CAFEAcA9Q-DKtH6UKH3R=er19jqxQRERGqLWogSL0YegdOTt6VA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--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 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.