All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
	virtualization@lists.linux-foundation.org
Cc: borntraeger@de.ibm.com, mst@redhat.com
Subject: Re: [PATCH V2 RFC 1/9] virtio_ring: change host notification API
Date: Tue, 29 Oct 2013 09:43:24 +1030	[thread overview]
Message-ID: <877gcxf0q3.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1382956242-23459-1-git-send-email-graalfs@linux.vnet.ibm.com>

Heinz Graalfs <graalfs@linux.vnet.ibm.com> writes:
> Rusty,
>
> here is just patch 1 (using bool as return value in notify API).
>
> Thanks.
>
> Heinz Graalfs (9):
>   virtio_ring: change host notification API
>   virtio_ring: let virtqueue_{kick()/notify()} return a bool
>   virtio_net: verify if virtqueue_kick() succeeded
>   virtio_test: verify if virtqueue_kick() succeeded
>   virtio_ring: add new function virtqueue_is_broken()
>   virtio_blk: verify if queue is broken after virtqueue_get_buf()
>   virtio_console: verify if queue is broken after virtqueue_get_buf()
>   virtio_net: verify if queue is broken after virtqueue_get_buf()
>   virtio_scsi: verify if queue is broken after virtqueue_get_buf()

Thanks, I've applied all of these.

Cheers,
Rusty.

  parent reply	other threads:[~2013-10-28 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 10:30 [PATCH V2 RFC 1/9] virtio_ring: change host notification API Heinz Graalfs
2013-10-28 10:30 ` Heinz Graalfs
2013-10-28 23:13 ` Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-24 15:23 [PATCH V2 RFC 0/9] virtio: fix hang(loop) after hot-unplug vlan Heinz Graalfs
2013-10-24 15:23 ` [PATCH V2 RFC 1/9] virtio_ring: change host notification API Heinz Graalfs
2013-10-27 23:27   ` Rusty Russell

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=877gcxf0q3.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=borntraeger@de.ibm.com \
    --cc=graalfs@linux.vnet.ibm.com \
    --cc=mst@redhat.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 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.