All of lore.kernel.org
 help / color / mirror / Atom feed
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"
	<virtio-comment@lists.oasis-open.org>,
	Shahaf Shuler <shahafs@nvidia.com>,
	"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>
Subject: Re: [virtio-comment] Re: [PATCH] conformance: Add missing virtqueue reset conformance references
Date: Mon, 30 Oct 2023 07:11:52 -0400	[thread overview]
Message-ID: <20231030071109-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87wmv4qsqf.fsf@redhat.com>

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/


  reply	other threads:[~2023-10-30 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231027133236.1350124-1-parav@nvidia.com>
     [not found] ` <PH0PR12MB54810FFF99577FB6B7FEA51BDCDCA@PH0PR12MB5481.namprd12.prod.outlook.com>
     [not found]   ` <20231027102358-mutt-send-email-mst@kernel.org>
     [not found]     ` <87bkckrva2.fsf@redhat.com>
2023-10-30 11:01       ` [virtio-comment] Re: [PATCH] conformance: Add missing virtqueue reset conformance references Cornelia Huck
2023-10-30 11:11         ` Michael S. Tsirkin [this message]
2023-10-30 11:46           ` 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=20231030071109-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=parav@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=xuanzhuo@linux.alibaba.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.