From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: borntraeger@de.ibm.com, linux-s390@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] virtio/s390 patches for 4.8
Date: Thu, 7 Jul 2016 19:42:52 +0300 [thread overview]
Message-ID: <20160707194246-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1467904077-1887-1-git-send-email-cornelia.huck@de.ibm.com>
On Thu, Jul 07, 2016 at 05:07:55PM +0200, Cornelia Huck wrote:
> Michael,
>
> here are two virtio/s390 patches for 4.8.
>
> First, Jing Liu noticed that she could trigger panics while playing
> around with hvc0 as preferred console but no virtio console: This
> can be fixed by not discarding our early_put_chars after init (as
> the minimal fix).
>
> This made us wonder why we still have that code around when no current
> host code supports the old transport: We have no idea whether this
> still works, and it's probably a good idea to put a deprecation
> message in there to check whether anyone screams.
>
> Patches are against your vhost branch.
thanks!
> Christian Borntraeger (1):
> virtio/s390: keep early_put_chars
>
> Cornelia Huck (1):
> virtio/s390: deprecate old transport
>
> arch/s390/Kconfig | 13 +++++++++++++
> drivers/s390/virtio/Makefile | 6 +++++-
> drivers/s390/virtio/kvm_virtio.c | 4 +++-
> 3 files changed, 21 insertions(+), 2 deletions(-)
>
> --
> 2.6.6
next prev parent reply other threads:[~2016-07-07 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 15:07 [PATCH 0/2] virtio/s390 patches for 4.8 Cornelia Huck
2016-07-07 15:07 ` [PATCH 1/2] virtio/s390: keep early_put_chars Cornelia Huck
2016-07-07 15:07 ` [PATCH 2/2] virtio/s390: deprecate old transport Cornelia Huck
2016-07-07 16:42 ` Michael S. Tsirkin [this message]
2016-08-08 11:39 ` [PATCH 0/2] virtio/s390 patches for 4.8 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=20160707194246-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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).