From: Kevin Traynor <ktraynor@redhat.com>
To: Michael Baum <michaelba@nvidia.com>, stable@dpdk.org
Cc: Matan Azrad <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH 21.11 0/2] net/mlx5: LRO fixes
Date: Thu, 19 May 2022 14:59:35 +0100 [thread overview]
Message-ID: <d8eb63c2-53ef-b67c-40bf-1cff330f4e2c@redhat.com> (raw)
In-Reply-To: <20220515131826.763915-1-michaelba@nvidia.com>
On 15/05/2022 14:18, Michael Baum wrote:
> Independent fixes about LRO.
>
> Michael Baum (2):
> net/mlx5: fix LRO validation in Rx setup
> net/mlx5: fix LRO configuration in drop Rx queue
>
> drivers/net/mlx5/mlx5_devx.c | 4 +++-
> drivers/net/mlx5/mlx5_rxq.c | 8 ++++++++
> 2 files changed, 11 insertions(+), 1 deletion(-)
>
Thanks Michael, applied.
prev parent reply other threads:[~2022-05-19 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 13:18 Michael Baum
2022-05-15 13:18 ` [PATCH 21.11 1/2] net/mlx5: fix LRO validation in Rx setup Michael Baum
2022-05-15 13:18 ` [PATCH 21.11 2/2] net/mlx5: fix LRO configuration in drop Rx queue Michael Baum
2022-05-19 13:59 ` Kevin Traynor [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=d8eb63c2-53ef-b67c-40bf-1cff330f4e2c@redhat.com \
--to=ktraynor@redhat.com \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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 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).