qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
	"Anthony Liguori" <aliguori@us.ibm.com>,
	"Aurélien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PULL 0/2] virtio-ccw patches 2013-03-18
Date: Tue, 19 Mar 2013 09:02:54 +0100	[thread overview]
Message-ID: <20130319090254.67774785@gondolin> (raw)
In-Reply-To: <1363622682-13996-1-git-send-email-cornelia.huck@de.ibm.com>

On Mon, 18 Mar 2013 17:04:40 +0100
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:

Hm, skip this. This clashes with the virtio-blk refactoring.

> The following changes since commit 225dc991b03f0f034aa348f5cf499de9d0979107:
> 
>   s390: Fix cpu refactoring fallout. (2013-03-17 20:01:31 +0000)
> 
> are available in the git repository at:
> 
>   git://github.com/cohuck/qemu virtio-ccw-upstr
> 
> for you to fetch changes up to 06964ad5dfff4ea3f8536be4730a8b501113e3c1:
> 
>   s390-virtio, virtio-ccw: Add config_wce for virtio-blk. (2013-03-18 13:06:09 +0100)
> 
> ----------------------------------------------------------------
> Cornelia Huck (2):
>       virtio-ccw: Add missing blk chs properties.
>       s390-virtio, virtio-ccw: Add config_wce for virtio-blk.
> 
>  hw/s390x/s390-virtio-bus.c |    1 +
>  hw/s390x/virtio-ccw.c      |    2 ++
>  2 files changed, 3 insertions(+)
> 

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 16:04 [Qemu-devel] [PULL 0/2] virtio-ccw patches 2013-03-18 Cornelia Huck
2013-03-18 16:04 ` [Qemu-devel] [PATCH 1/2] virtio-ccw: Add missing blk chs properties Cornelia Huck
2013-03-18 16:04 ` [Qemu-devel] [PATCH 2/2] s390-virtio, virtio-ccw: Add config_wce for virtio-blk Cornelia Huck
2013-03-19  8:02 ` Cornelia Huck [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=20130319090254.67774785@gondolin \
    --to=cornelia.huck@de.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.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 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).