public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
	"cohuck@redhat.com" <cohuck@redhat.com>,
	Shahaf Shuler <shahafs@nvidia.com>
Subject: Re: [PATCH v1 0/5] Assorted editorial fixes
Date: Mon, 16 Sep 2024 04:35:04 -0400	[thread overview]
Message-ID: <20240916043440-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <IA0PR12MB87130A72951032F2936544B1DC602@IA0PR12MB8713.namprd12.prod.outlook.com>

On Mon, Sep 16, 2024 at 03:11:10AM +0000, Parav Pandit wrote:
> Hi Michael, Cornelia,
> 
> > From: Parav Pandit <parav@nvidia.com>
> > Sent: Monday, September 16, 2024 8:39 AM
> > To: virtio-comment@lists.linux.dev; mst@redhat.com; cohuck@redhat.com
> > Cc: Shahaf Shuler <shahafs@nvidia.com>; Parav Pandit <parav@nvidia.com>
> > Subject: [PATCH v1 0/5] Assorted editorial fixes
> > 
> > This series covers assorted editorial fixes to fix name, adding missing struct
> > and fix spelling errors.
> > 
> > changelog:
> > v0->v1:
> > - added Reviewed-by of Matias Ezequiel Vara Larsen
> > - added github issue link
> >
> 
> Please open a voting ballot for these fixes.
> The github link is: https://lore.kernel.org/virtio-comment/20240916030835.68178-1-parav@nvidia.com/T/#t

yes but everyone is at plumbers/kvm forum.
Pls request it in a week's time, ok?

> 
>  
> > Parav Pandit (5):
> >   device-parts: editorial: Add missing struct keyword
> >   device-parts: editorial: Fix metadata type name
> >   crypto: editorial: Fix spelling errors
> >   gpu: editorial: Fix spelling errors
> >   common: editorial: Fix spelling errors
> > 
> >  admin-cmds-device-parts.tex         |  6 +++---
> >  admin.tex                           |  2 +-
> >  content.tex                         |  4 ++--
> >  device-types/crypto/description.tex | 10 +++++-----
> >  device-types/gpu/description.tex    |  4 ++--
> >  5 files changed, 13 insertions(+), 13 deletions(-)
> > 
> > --
> > 2.34.1


  reply	other threads:[~2024-09-16  8:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  3:08 [PATCH v1 0/5] Assorted editorial fixes Parav Pandit
2024-09-16  3:08 ` [PATCH v1 1/5] device-parts: editorial: Add missing struct keyword Parav Pandit
2024-09-16  3:08 ` [PATCH v1 2/5] device-parts: editorial: Fix metadata type name Parav Pandit
2024-09-16  3:08 ` [PATCH v1 3/5] crypto: editorial: Fix spelling errors Parav Pandit
2024-09-16  3:08 ` [PATCH v1 4/5] gpu: " Parav Pandit
2024-09-16  3:08 ` [PATCH v1 5/5] common: " Parav Pandit
2024-09-16  3:11 ` [PATCH v1 0/5] Assorted editorial fixes Parav Pandit
2024-09-16  8:35   ` Michael S. Tsirkin [this message]
2024-09-16  9:13     ` Parav Pandit
2024-09-25 11:33     ` 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=20240916043440-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.linux.dev \
    /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