Re: [virtio-comment] Re: [PATCH] conformance: Add missing virtqueue reset conformance references

Re: [virtio-comment] Re: [PATCH] conformance: Add missing virtqueue reset conformance references

[Cornelia Huck]

On Fri, Oct 27 2023, Cornelia Huck <cohuck@redhat.com> wrote:

> On Fri, Oct 27 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
>> I think we can merge it as editorial actually. Cornelia?
>
> I agree. (Someone should probably merge the voted issues on the 1.4
> branch first.)

But what I'll do is removing the "Fixes:" line and close the github
issue manually. We should use github issues for voting only, not for
editorial changes (we need some way to distinguish between the two, and
I'd rather have a straightforward way to do so.)


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/

Re: [virtio-comment] Re: [PATCH] conformance: Add missing virtqueue reset conformance references

[Michael S. Tsirkin]

On Mon, Oct 30, 2023 at 12:01:28PM +0100, Cornelia Huck wrote:
> On Fri, Oct 27 2023, Cornelia Huck <cohuck@redhat.com> wrote:
> 
> > On Fri, Oct 27 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >> I think we can merge it as editorial actually. Cornelia?
> >
> > I agree. (Someone should probably merge the voted issues on the 1.4
> > branch first.)
> 
> But what I'll do is removing the "Fixes:" line and close the github
> issue manually. We should use github issues for voting only, not for
> editorial changes (we need some way to distinguish between the two, and
> I'd rather have a straightforward way to do so.)

Agree totally, that seems like the best way to do it.
If this begins to happen a lot we can add an "editorial" tag though.


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/

RE: [virtio-comment] Re: [PATCH] conformance: Add missing virtqueue reset conformance references

[Parav Pandit]

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Monday, October 30, 2023 4:42 PM
> 
> On Mon, Oct 30, 2023 at 12:01:28PM +0100, Cornelia Huck wrote:
> > On Fri, Oct 27 2023, Cornelia Huck <cohuck@redhat.com> wrote:
> >
> > > On Fri, Oct 27 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > >> I think we can merge it as editorial actually. Cornelia?
> > >
> > > I agree. (Someone should probably merge the voted issues on the 1.4
> > > branch first.)
> >
> > But what I'll do is removing the "Fixes:" line and close the github
> > issue manually. We should use github issues for voting only, not for
> > editorial changes (we need some way to distinguish between the two,
> > and I'd rather have a straightforward way to do so.)
> 
> Agree totally, that seems like the best way to do it.
> If this begins to happen a lot we can add an "editorial" tag though.

Thanks.

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/