All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Wang <wei.w.wang@intel.com>
To: Cornelia Huck <cohuck@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>
Cc: virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, virtio-dev@lists.oasis-open.org,
	Halil Pasic <pasic@linux.ibm.com>
Subject: [virtio-dev] Re: [PATCH 1/2] virtio: fix virtio_config_ops description
Date: Tue, 15 Jan 2019 10:15:39 +0800	[thread overview]
Message-ID: <5C3D424B.70400@intel.com> (raw)
In-Reply-To: <20190114150958.39a4a56a.cohuck@redhat.com>

On 01/14/2019 10:09 PM, Cornelia Huck wrote:
> On Thu,  3 Jan 2019 17:08:03 +0100
> Cornelia Huck <cohuck@redhat.com> wrote:
>
>> - get_features has returned 64 bits since commit d025477368792
>>    ("virtio: add support for 64 bit features.")
>> - properly mark all optional callbacks
>>
>> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
>> ---
>>   include/linux/virtio_config.h | 8 ++++----
>>   1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/include/linux/virtio_config.h b/include/linux/virtio_config.h
>> index 32baf8e26735..7087ef946ba7 100644
>> --- a/include/linux/virtio_config.h
>> +++ b/include/linux/virtio_config.h
>> @@ -22,7 +22,7 @@ struct irq_affinity;
>>    *	offset: the offset of the configuration field
>>    *	buf: the buffer to read the field value from.
>>    *	len: the length of the buffer
>> - * @generation: config generation counter
>> + * @generation: config generation counter (optional)
>>    *	vdev: the virtio_device
>>    *	Returns the config generation counter
>>    * @get_status: read the status byte
>> @@ -48,17 +48,17 @@ struct irq_affinity;
>>    * @del_vqs: free virtqueues found by find_vqs().
>>    * @get_features: get the array of feature bits for this device.
>>    *	vdev: the virtio_device
>> - *	Returns the first 32 feature bits (all we currently need).
>> + *	Returns the first 64 feature bits (all we currently need).
>>    * @finalize_features: confirm what device features we'll be using.
>>    *	vdev: the virtio_device
>>    *	This gives the final feature bits for the device: it can change
>>    *	the dev->feature bits if it wants.
>>    *	Returns 0 on success or error status
>> - * @bus_name: return the bus name associated with the device
>> + * @bus_name: return the bus name associated with the device (optional)
>>    *	vdev: the virtio_device
>>    *      This returns a pointer to the bus name a la pci_name from which
>>    *      the caller can then copy.
>> - * @set_vq_affinity: set the affinity for a virtqueue.
>> + * @set_vq_affinity: set the affinity for a virtqueue (optional).
>>    * @get_vq_affinity: get the affinity for a virtqueue (optional).
>>    */
>>   typedef void vq_callback_t(struct virtqueue *);
> Ping. Any feedback on that patch?

Reviewed-by: Wei Wang <wei.w.wang@intel.com>

Best,
Wei


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  parent reply	other threads:[~2019-01-15  2:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 16:08 [virtio-dev] [PATCH 0/2] virtio: virtio_config_ops documentation Cornelia Huck
2019-01-03 16:08 ` [PATCH 1/2] virtio: fix virtio_config_ops description Cornelia Huck
2019-01-03 16:08 ` [virtio-dev] " Cornelia Huck
2019-01-14 14:09   ` Cornelia Huck
2019-01-14 14:09   ` [virtio-dev] " Cornelia Huck
2019-01-14 14:57     ` Halil Pasic
2019-01-15  2:15     ` Wei Wang [this message]
2019-01-15  2:20       ` Michael S. Tsirkin
2019-01-15  2:20       ` Michael S. Tsirkin
2019-01-15  2:15     ` Wei Wang
2019-01-03 16:08 ` [PATCH 2/2] virtio: document virtio_config_ops restrictions Cornelia Huck
2019-01-03 16:08 ` [virtio-dev] " Cornelia Huck
2019-01-03 16:28   ` Michael S. Tsirkin
2019-01-03 16:28   ` [virtio-dev] " Michael S. Tsirkin
2019-01-04 12:39     ` Cornelia Huck
2019-01-04 12:39     ` Cornelia Huck
2019-01-03 17:28   ` [virtio-dev] " Halil Pasic
2019-01-04 12:48     ` Cornelia Huck
2019-01-04 12:48       ` Cornelia Huck
2019-01-15  2:18   ` [virtio-dev] " Wei Wang
2019-01-15  2:18   ` Wei Wang

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=5C3D424B.70400@intel.com \
    --to=wei.w.wang@intel.com \
    --cc=cohuck@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=virtio-dev@lists.oasis-open.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 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.