From: Cornelia Huck <cohuck@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Alexander Graf <agraf@suse.de>, Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
imbrenda@linux.vnet.ibm.com, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] s390x/sclp: fix maxram calculation
Date: Tue, 31 Jul 2018 12:48:09 +0200 [thread overview]
Message-ID: <20180731124809.0502bcb9.cohuck@redhat.com> (raw)
In-Reply-To: <20180731085205.2637da26.cohuck@redhat.com>
On Tue, 31 Jul 2018 08:52:05 +0200
Cornelia Huck <cohuck@redhat.com> wrote:
> On Mon, 30 Jul 2018 11:58:13 -0500
> Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
>
> > Quoting Christian Borntraeger (2018-07-30 10:31:12)
> > > Are we still able to get things into 2.12.1 or are we too late?
> >
> > Freeze is EOD today, but I can grab them if they hit master/rc3 tomorrow.
>
> OK, I just sent a pull request with this patch.
...and it is in master now.
next prev parent reply other threads:[~2018-07-31 10:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 14:09 [Qemu-devel] [PATCH 1/1] s390x/sclp: fix maxram calculation Christian Borntraeger
2018-07-30 14:34 ` David Hildenbrand
2018-07-30 15:00 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-07-30 15:17 ` David Hildenbrand
2018-07-30 15:20 ` Christian Borntraeger
2018-07-30 15:28 ` David Hildenbrand
2018-07-30 15:32 ` Cornelia Huck
2018-07-30 15:31 ` [Qemu-devel] " Christian Borntraeger
2018-07-30 16:58 ` Michael Roth
2018-07-31 6:52 ` Cornelia Huck
2018-07-31 10:48 ` Cornelia Huck [this message]
2018-07-30 15:43 ` David Hildenbrand
2018-07-30 15:47 ` Cornelia Huck
2018-07-31 8:34 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2018-07-30 15:55 ` [Qemu-devel] " 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=20180731124809.0502bcb9.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=qemu-stable@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.