All of lore.kernel.org
 help / color / mirror / Atom feed
From: "KONRAD Frédéric" <fred.konrad@greensocs.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 0/3] virtio-ccw queue as of 2013/03/20
Date: Wed, 20 Mar 2013 09:03:13 +0100	[thread overview]
Message-ID: <51496D41.9060409@greensocs.com> (raw)
In-Reply-To: <1363765425-5746-1-git-send-email-cornelia.huck@de.ibm.com>

On 20/03/2013 08:43, Cornelia Huck wrote:
> Hi,
>
> here are again my patches adding missing virtio-blk properties
> for the s390 transports, this time rebased on top of the virtio-blk
> refactoring.
>
> The third patch is new, bringing s390-virtio and virtio-ccw in line
> with virtio-pci.
>
> Alex, again I'd like an ack from you (for the new patch) so I can
> take this through my tree.
>
> Cornelia Huck (3):
>    virtio-ccw: Add missing blk chs properties.
>    s390-virtio, virtio-ccw: Add config_wce for virtio-blk.
>    virtio-ccw, s390-virtio: Use generic virtio-blk macro.
>
>   hw/s390x/s390-virtio-bus.c |    7 +------
>   hw/s390x/virtio-ccw.c      |    6 +-----
>   2 files changed, 2 insertions(+), 11 deletions(-)
>
Can I be CC'ed when this goes in?

Thanks,
Fred

  parent reply	other threads:[~2013-03-20  8:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20  7:43 [Qemu-devel] [PATCH 0/3] virtio-ccw queue as of 2013/03/20 Cornelia Huck
2013-03-20  7:43 ` [Qemu-devel] [PATCH 1/3] virtio-ccw: Add missing blk chs properties Cornelia Huck
2013-03-20  7:43 ` [Qemu-devel] [PATCH 2/3] s390-virtio, virtio-ccw: Add config_wce for virtio-blk Cornelia Huck
2013-03-20  7:43 ` [Qemu-devel] [PATCH 3/3] virtio-ccw, s390-virtio: Use generic virtio-blk macro Cornelia Huck
2013-03-20  8:03 ` KONRAD Frédéric [this message]
2013-03-20  8:09   ` [Qemu-devel] [PATCH 0/3] virtio-ccw queue as of 2013/03/20 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=51496D41.9060409@greensocs.com \
    --to=fred.konrad@greensocs.com \
    --cc=agraf@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=qemu-devel@nongnu.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 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.