From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <rth@twiddle.net>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] s390x fixes (post 2.11)
Date: Wed, 22 Nov 2017 15:46:44 +0100 [thread overview]
Message-ID: <20171122154644.4a81b1f3.cohuck@redhat.com> (raw)
In-Reply-To: <20171122142627.73170-1-borntraeger@de.ibm.com>
On Wed, 22 Nov 2017 15:26:25 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Christian Borntraeger (2):
> s390x/migration: use zero flag parameter
> pc-bios/s390-ccw: zero out bss section
>
> pc-bios/s390-ccw/start.S | 30 +++++++++++++++++++++++++++---
> target/s390x/kvm.c | 16 ++++++++--------
> 2 files changed, 35 insertions(+), 11 deletions(-)
>
I'm inclined to queue these two to s390-next (commit messages changed)
so they get some exposure.
next prev parent reply other threads:[~2017-11-22 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 14:26 [Qemu-devel] [PATCH 0/2] s390x fixes (post 2.11) Christian Borntraeger
2017-11-22 14:26 ` [Qemu-devel] [PATCH 1/2] s390x/migration: use zero flag parameter Christian Borntraeger
2017-11-22 14:37 ` Thomas Huth
2017-11-22 14:49 ` Cornelia Huck
2017-11-22 14:43 ` Cornelia Huck
2017-11-22 14:50 ` Christian Borntraeger
2017-11-22 14:26 ` [Qemu-devel] [PATCH 2/2] pc-bios/s390-ccw: zero out bss section Christian Borntraeger
2017-11-22 14:45 ` Cornelia Huck
2017-11-22 16:36 ` Thomas Huth
2017-11-23 7:32 ` Richard Henderson
2017-11-22 14:46 ` Cornelia Huck [this message]
2017-11-22 14:54 ` [Qemu-devel] [PATCH 0/2] s390x fixes (post 2.11) no-reply
2017-11-22 15:07 ` Christian Borntraeger
2017-11-22 15:45 ` Cornelia Huck
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=20171122154644.4a81b1f3.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.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.