From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
virtio-comment@lists.oasis-open.org, david.edmondson@oracle.com,
virtio-dev@lists.oasis-open.org, sburla@marvell.com,
jasowang@redhat.com, yishaih@nvidia.com, maorg@nvidia.com,
shahafs@nvidia.com
Subject: [virtio-comment] Re: [PATCH v14] admin: Add group member legacy register access commands
Date: Tue, 11 Jul 2023 05:14:18 -0400 [thread overview]
Message-ID: <20230711051109-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87pm4ylspa.fsf@redhat.com>
On Tue, Jul 11, 2023 at 11:10:09AM +0200, Cornelia Huck wrote:
> On Mon, Jul 10 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Mon, Jul 10, 2023 at 07:17:52PM +0300, Parav Pandit wrote:
> >> +The \field{flags} value of 0x1 indicates that the notification address is of
> >> +the owner device, value of 0x2 indicates that the notification address is of
> >> +the member device, the value of 0 indicates that all the entries starting from
> >
> > , the -> and value of 0x0
>
> Looking at this sentence again, maybe make this
>
> "A \field{flags} value of 0x1 indicates that the notification address is
> that of the owner device, a value of 0x2 indicates that the notification
> address is that of the member device, and a value of 0 indicates..."
>
> if you're tweaking it anyway?
Oh yes, of course. Ack to that.
> >
> >
> >> +that entry are invalid entries in \field{entries}. All other values in
> >> +\field{flags} are reserved.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
virtio-comment@lists.oasis-open.org, david.edmondson@oracle.com,
virtio-dev@lists.oasis-open.org, sburla@marvell.com,
jasowang@redhat.com, yishaih@nvidia.com, maorg@nvidia.com,
shahafs@nvidia.com
Subject: [virtio-dev] Re: [PATCH v14] admin: Add group member legacy register access commands
Date: Tue, 11 Jul 2023 05:14:18 -0400 [thread overview]
Message-ID: <20230711051109-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87pm4ylspa.fsf@redhat.com>
On Tue, Jul 11, 2023 at 11:10:09AM +0200, Cornelia Huck wrote:
> On Mon, Jul 10 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Mon, Jul 10, 2023 at 07:17:52PM +0300, Parav Pandit wrote:
> >> +The \field{flags} value of 0x1 indicates that the notification address is of
> >> +the owner device, value of 0x2 indicates that the notification address is of
> >> +the member device, the value of 0 indicates that all the entries starting from
> >
> > , the -> and value of 0x0
>
> Looking at this sentence again, maybe make this
>
> "A \field{flags} value of 0x1 indicates that the notification address is
> that of the owner device, a value of 0x2 indicates that the notification
> address is that of the member device, and a value of 0 indicates..."
>
> if you're tweaking it anyway?
Oh yes, of course. Ack to that.
> >
> >
> >> +that entry are invalid entries in \field{entries}. All other values in
> >> +\field{flags} are reserved.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-07-11 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 16:17 [virtio-comment] [PATCH v14] admin: Add group member legacy register access commands Parav Pandit
2023-07-10 16:17 ` [virtio-dev] " Parav Pandit
2023-07-10 16:35 ` [virtio-comment] " Michael S. Tsirkin
2023-07-10 16:35 ` [virtio-dev] " Michael S. Tsirkin
2023-07-10 16:57 ` [virtio-comment] " Parav Pandit
2023-07-10 16:57 ` [virtio-dev] " Parav Pandit
2023-07-11 9:10 ` [virtio-comment] " Cornelia Huck
2023-07-11 9:10 ` [virtio-dev] " Cornelia Huck
2023-07-11 9:14 ` Michael S. Tsirkin [this message]
2023-07-11 9:14 ` Michael S. Tsirkin
2023-07-11 15:02 ` [virtio-comment] " Parav Pandit
2023-07-11 15:02 ` [virtio-dev] " Parav Pandit
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=20230711051109-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=jasowang@redhat.com \
--cc=maorg@nvidia.com \
--cc=parav@nvidia.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=yishaih@nvidia.com \
/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.