All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>,
	virtio-comment@lists.oasis-open.org, oren@nvidia.com,
	stefanha@redhat.com, eperezma@redhat.com
Subject: [virtio-comment] Re: [PATCH v2 1/1] Fix reserved Feature bits numbering
Date: Tue, 04 Jan 2022 09:10:48 +0100	[thread overview]
Message-ID: <87k0ffx6nr.fsf@redhat.com> (raw)
In-Reply-To: <20220103164709-mutt-send-email-mst@kernel.org>

On Mon, Jan 03 2022, "Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Mon, Jan 03, 2022 at 06:20:45PM +0100, Cornelia Huck wrote:
>> On Mon, Jan 03 2022, Max Gurtovoy <mgurtovoy@nvidia.com> wrote:
>> 
>> > This should have been updated during VIRTIO_F_NOTIFICATION_DATA,
>> > VIRTIO_F_NOTIF_CONFIG_DATA and VIRTIO_F_RING_RESET standartization.
>> >
>> > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>> > Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
>> 
>> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/128
>> 
>> Can you please also update the archive link in the issue, once the mail
>> shows up there?
>
>
> Wish we had a cleaner way to do it than updating this each time we
> add a generic feature bit.

Indeed. But let's just go with this fixup until we come up with a better
way.


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/


      reply	other threads:[~2022-01-04  8:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 17:03 [PATCH v2 1/1] Fix reserved Feature bits numbering Max Gurtovoy
2022-01-03 17:20 ` [virtio-comment] " Cornelia Huck
2022-01-03 17:42   ` Max Gurtovoy
2022-01-03 21:48   ` Michael S. Tsirkin
2022-01-04  8:10     ` 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=87k0ffx6nr.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=mgurtovoy@nvidia.com \
    --cc=mst@redhat.com \
    --cc=oren@nvidia.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-comment@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 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.