From: Greg KH <gregkh@linuxfoundation.org>
To: Eli Cohen <elic@nvidia.com>
Cc: mst@redhat.com, netdev@vger.kernel.org, stable@vger.kernel.org,
virtualization@lists.linux-foundation.org, si-wei.liu@oracle.com
Subject: Re: [PATCH 0/5] VDPA mlx5 fixes
Date: Thu, 8 Apr 2021 11:17:28 +0200 [thread overview]
Message-ID: <YG7KKI+8Z6ocGwNf@kroah.com> (raw)
In-Reply-To: <20210408091047.4269-1-elic@nvidia.com>
On Thu, Apr 08, 2021 at 12:10:42PM +0300, Eli Cohen wrote:
> Hi Michael,
>
> The following series contains fixes to mlx5 vdpa driver. Included first
> is Siwei's fix to queried MTU was already reviewed a while ago and is
> not in your tree.
>
> Patches 2 and 3 are required to allow mlx5_vdpa run on sub functions.
>
> This series contains patches that were included in Parav's series
> http://lists.infradead.org/pipermail/linux-mtd/2016-January/064878.html
> but that series will be sent again at a later time.
>
> Eli Cohen (4):
> vdpa/mlx5: Use the correct dma device when registering memory
> vdpa/mlx5: Retrieve BAR address suitable any function
> vdpa/mlx5: Fix wrong use of bit numbers
> vdpa/mlx5: Fix suspend/resume index restoration
>
> Si-Wei Liu (1):
> vdpa/mlx5: should exclude header length and fcs from mtu
>
> drivers/vdpa/mlx5/core/mlx5_vdpa.h | 4 +++
> drivers/vdpa/mlx5/core/mr.c | 9 +++++--
> drivers/vdpa/mlx5/core/resources.c | 3 ++-
> drivers/vdpa/mlx5/net/mlx5_vnet.c | 40 ++++++++++++++++++------------
> 4 files changed, 37 insertions(+), 19 deletions(-)
>
> --
> 2.30.1
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next parent reply other threads:[~2021-04-08 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210408091047.4269-1-elic@nvidia.com>
2021-04-08 9:17 ` Greg KH [this message]
[not found] ` <20210408091047.4269-3-elic@nvidia.com>
2021-04-08 9:44 ` [PATCH 2/5] vdpa/mlx5: Use the correct dma device when registering memory Jason Wang
[not found] ` <20210408091047.4269-4-elic@nvidia.com>
2021-04-08 9:45 ` [PATCH 3/5] vdpa/mlx5: Retrieve BAR address suitable any function Jason Wang
[not found] ` <20210408091047.4269-6-elic@nvidia.com>
2021-04-08 9:45 ` [PATCH 5/5] vdpa/mlx5: Fix suspend/resume index restoration Jason Wang
[not found] ` <20210408091047.4269-5-elic@nvidia.com>
2021-04-08 9:46 ` [PATCH 4/5] vdpa/mlx5: Fix wrong use of bit numbers Jason Wang
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=YG7KKI+8Z6ocGwNf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=elic@nvidia.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=si-wei.liu@oracle.com \
--cc=stable@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).