Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>,
	Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-comment] Re: [PATCH] changelog: Fix missing reference to driver notifications
Date: Thu, 16 Feb 2023 18:42:41 -0500	[thread overview]
Message-ID: <20230216184217-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54812E87A2EE7C14D72C3FE2DCA09@PH0PR12MB5481.namprd12.prod.outlook.com>

On Thu, Feb 16, 2023 at 09:13:12PM +0000, Parav Pandit wrote:
> 
> > From: Cornelia Huck <cohuck@redhat.com>
> > Sent: Thursday, February 16, 2023 3:01 AM
> > 
> > On Thu, Feb 16 2023, Parav Pandit <parav@nvidia.com> wrote:
> > 
> > > Cited commit in fixes tag missed to update the reference to drivers
> > > notifications section in past change log.
> > > Fix the reference.
> > >
> > > Fixes: be2ce1ee17e0 ("content.tex Fix Driver notifications label")
> > > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > > ---
> > >  cl-os.tex | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > Does it really make sense to patch the changelog? This is about the
> > 1.1->1.2 changes, and I'd assume it is only relevant for the released
> > 1.2 spec. We'll replace the changelog anyway when we do the 1.3 release.
> >
> Right. I got it.
> It should be fine to drop this patch.
> I took a blind scan to make sure all the previous links exists now.
> It isn't necessary from 1.2 to 1.3 as those entries will be removed as you say.

Right just post a patch to drop all of cl-os.tex.

> > [Speaking of the 1.3 release, we really should be planning for it. Maybe target
> > June or so, with a freeze in April?]
> Very good point. Yes.
> Not fully familiar yet, if its June end, may be May is alright too depending on changes in coming months.
> I am sure you and Michael are better place to make this call.



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-02-16 23:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  5:34 [PATCH] changelog: Fix missing reference to driver notifications Parav Pandit
2023-02-16  8:01 ` [virtio-dev] " Cornelia Huck
2023-02-16 21:13   ` Parav Pandit
2023-02-16 23:42     ` Michael S. Tsirkin [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=20230216184217-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=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