virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
	linux-s390@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/3] virtio-ccw: updates
Date: Mon, 21 Jan 2019 14:30:31 -0500	[thread overview]
Message-ID: <20190121143020-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190121121944.12309-1-cohuck@redhat.com>

On Mon, Jan 21, 2019 at 01:19:41PM +0100, Cornelia Huck wrote:
> [Now not as pull request, as requested. The first patch had already been
> in my last pull request. Patches are against master, but should apply
> basically anywhere.
> 
> Git branch:
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git virtio-ccw]
> 
> Some updates: documentation, gracefully handle invalid queues, and wire
> up the ->bus_name callback (which had somehow fallen through the cracks.)

Thanks, will queue.

> Cornelia Huck (2):
>   virtio-ccw: diag 500 may return a negative cookie
>   virtio-ccw: wire up ->bus_name callback
> 
> Halil Pasic (1):
>   s390/virtio: handle find on invalid queue gracefully
> 
>  Documentation/virtual/kvm/s390-diag.txt |  3 ++-
>  drivers/s390/virtio/virtio_ccw.c        | 12 +++++++++++-
>  2 files changed, 13 insertions(+), 2 deletions(-)
> 
> -- 
> 2.17.2

      parent reply	other threads:[~2019-01-21 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 12:19 [PATCH 0/3] virtio-ccw: updates Cornelia Huck
2019-01-21 12:19 ` [PATCH 1/3] virtio-ccw: diag 500 may return a negative cookie Cornelia Huck
2019-01-21 12:19 ` [PATCH 2/3] s390/virtio: handle find on invalid queue gracefully Cornelia Huck
2019-01-21 12:19 ` [PATCH 3/3] virtio-ccw: wire up ->bus_name callback Cornelia Huck
2019-01-21 19:30 ` Michael S. Tsirkin [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=20190121143020-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.com \
    --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).