Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: David Edmondson <david.edmondson@oracle.com>
To: Parav Pandit <parav@nvidia.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
	"cohuck@redhat.com" <cohuck@redhat.com>
Cc: "sgarzare@redhat.com" <sgarzare@redhat.com>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>,
	Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] RE: [virtio-comment] [PATCH v8 5/8] transport-ccw: Rename queue depth/size to other transports
Date: Tue, 28 Mar 2023 17:16:34 +0100	[thread overview]
Message-ID: <m2pm8sc0m5.fsf@oracle.com> (raw)
In-Reply-To: <PH0PR12MB5481B571104CA387FCB74EA7DC889@PH0PR12MB5481.namprd12.prod.outlook.com>

Parav Pandit <parav@nvidia.com> writes:

>> From: David Edmondson <david.edmondson@oracle.com>
>> Sent: Tuesday, March 28, 2023 10:07 AM
>> > --- a/transport-ccw.tex
>> > +++ b/transport-ccw.tex
>> > @@ -237,12 +237,12 @@ \subsubsection{Configuring a
>> > Virtqueue}\label{sec:Virtio Transport Options / Vir
>> > \begin{lstlisting}  struct vq_config_block {
>> >          be16 index;
>> > -        be16 max_num;
>> > +        be16 max_queue_size; /* Previously named as max_num */
>> 
>> "named as" doesn't feel like typical language use - you can remove "as", though
>> I'd be inclined to use some kind of decoration for the name:
>> 
>> /* Previously named 'max_num'. */
>> 
>> >  };
>> >  \end{lstlisting}
>
> I really don't see any value in putting this change log material in the spec section,
> But anyways, Michael finds its useful for some users,
>
> So how about, 
>
> /* Previously known as max_num. */

Seems fine.
-- 
And now I know what every step is for.

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


  reply	other threads:[~2023-03-28 16:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 23:59 [virtio-dev] [PATCH v8 0/8] Rename queue index to queue number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] [PATCH v8 1/8] content: Add vq number text Parav Pandit
2023-03-28 13:56   ` David Edmondson
2023-03-28 14:00     ` [virtio-dev] RE: [virtio-comment] " Parav Pandit
2023-03-27 23:59 ` [virtio-dev] [PATCH v8 2/8] transport-pci: Refer to the vq by its number Parav Pandit
2023-03-28 13:58   ` David Edmondson
2023-03-27 23:59 ` [virtio-dev] [PATCH v8 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-28 14:01   ` [virtio-dev] Re: [virtio-comment] " David Edmondson
2023-03-27 23:59 ` [virtio-dev] [PATCH v8 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-28 14:05   ` [virtio-dev] Re: [virtio-comment] " David Edmondson
2023-03-27 23:59 ` [virtio-dev] [PATCH v8 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-28 14:07   ` [virtio-dev] Re: [virtio-comment] " David Edmondson
2023-03-28 15:04     ` [virtio-dev] " Parav Pandit
2023-03-28 16:16       ` David Edmondson [this message]
2023-03-28 16:18         ` Parav Pandit
2023-03-27 23:59 ` [virtio-dev] [PATCH v8 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] [PATCH v8 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-27 23:59 ` [virtio-dev] [PATCH v8 8/8] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-03-28 14:13   ` David Edmondson
2023-03-28 13:53 ` [virtio-dev] [PATCH v8 0/8] Rename queue index to queue number David Edmondson

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=m2pm8sc0m5.fsf@oracle.com \
    --to=david.edmondson@oracle.com \
    --cc=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.com \
    --cc=pasic@linux.ibm.com \
    --cc=sgarzare@redhat.com \
    --cc=shahafs@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.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