All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: parav@mellanox.com, virtualization@lists.linux-foundation.org,
	eperezma@redhat.com, Eli Cohen <elic@nvidia.com>
Subject: Re: [PATCH 0/1] posted interrtups support for mlx5
Date: Mon, 3 Apr 2023 14:10:33 -0400	[thread overview]
Message-ID: <20230403141005-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230403140728-mutt-send-email-mst@kernel.org>

On Mon, Apr 03, 2023 at 02:09:46PM -0400, Michael S. Tsirkin wrote:
> On Mon, Apr 03, 2023 at 01:00:16PM -0400, Parav Pandit wrote:
> > 
> > 
> > On 4/3/2023 12:20 PM, Eli Cohen wrote:
> > > Hi,
> > > 
> > > the single patch in this series adds support for posted interrupts in
> > > mlx5.
> > > 
> > > It depends on the patch series already accpted can be seen here:
> > > https://patchwork.kernel.org/project/netdevbpf/patch/20230324231341.29808-1-saeed@kernel.org/
> > > 
> > > git pull  git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git
> > > tags/mlx5-updates-2023-03-20
> > > 
> > > Eli Cohen (1):
> > >    vdpa/mlx5: Support interrupt bypassing
> > > 
> > >   drivers/vdpa/mlx5/net/mlx5_vnet.c | 139 ++++++++++++++++++++++++++++--
> > >   drivers/vdpa/mlx5/net/mlx5_vnet.h |  14 +++
> > >   2 files changed, 144 insertions(+), 9 deletions(-)
> > > 
> > In subject
> > 
> > s/interrtups/interrupts/
> 
> In fact if we are splitting hairs, this is a reduced relative (full form
> would be "support of posted interrupts") so it should not use a plural
> form. Also pls use a prefix in the patch subject. In the end:
> 	mlx5: posted interrupt support
> would be better.

Having said that, it's 0/1 so typos do not matter, they are not
in commit log.

-- 
MST

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

      reply	other threads:[~2023-04-03 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230403162039.18932-1-elic@nvidia.com>
     [not found] ` <20230403162039.18932-2-elic@nvidia.com>
2023-04-03 16:58   ` [PATCH 1/1] vdpa/mlx5: Support interrupt bypassing Parav Pandit via Virtualization
2023-04-03 18:11   ` Michael S. Tsirkin
2023-04-04  2:24   ` Jason Wang
     [not found]     ` <c12e67e9-2757-b1e3-93ae-f05df3774d03@nvidia.com>
2023-04-10  2:00       ` Jason Wang
     [not found]         ` <9200f3cc-aa57-c1ba-0d45-d6148eaa4533@nvidia.com>
2023-04-19  4:41           ` Jason Wang
     [not found]       ` <fd2c22a3-a9f3-b9a7-3669-a8ef5b0e0f3c@nvidia.com>
2023-04-10  2:02         ` Jason Wang
2023-04-03 17:00 ` [PATCH 0/1] posted interrtups support for mlx5 Parav Pandit via Virtualization
2023-04-03 18:09   ` Michael S. Tsirkin
2023-04-03 18:10     ` 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=20230403141005-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=elic@nvidia.com \
    --cc=eperezma@redhat.com \
    --cc=parav@mellanox.com \
    --cc=parav@nvidia.com \
    --cc=virtualization@lists.linux-foundation.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.