From: Long Li <longli@microsoft.com>
To: Sam Andrew <samandrew@microsoft.com>,
Alexander Skorichenko <askorichenko@netgate.com>
Cc: "stephen@networkplumber.org" <stephen@networkplumber.org>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>,
Wei Hu <weh@microsoft.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] Re: [PATCH] net/netvsc: fix mtu_set in netvsc devices
Date: Wed, 3 Jul 2024 22:57:49 +0000 [thread overview]
Message-ID: <PH7PR21MB3071E7194453C932F594FB4ACEDD2@PH7PR21MB3071.namprd21.prod.outlook.com> (raw)
In-Reply-To: <SN7PR21MB3953338A4C25803FF10F3635B5DD2@SN7PR21MB3953.namprd21.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]
Fixes: 45c83603087e (“net/netvsc: support MTU set”)
Cc: stable@dpdk.org<mailto:stable@dpdk.org>
From: Sam Andrew <samandrew@microsoft.com>
Sent: Wednesday, July 3, 2024 3:50 PM
To: Alexander Skorichenko <askorichenko@netgate.com>; Long Li <longli@microsoft.com>
Cc: stephen@networkplumber.org; ferruh.yigit@amd.com; andrew.rybchenko@oktetlabs.ru; Wei Hu <weh@microsoft.com>; dev@dpdk.org
Subject: RE: [EXTERNAL] Re: [PATCH] net/netvsc: fix mtu_set in netvsc devices
Thank you so much, Alexander. I’ve reviewed the patch. It looks good to me as well.
Reviewed-by: Sam Andrew <samandrew@microsoft.com<mailto:samandrew@microsoft.com>>
From: Alexander Skorichenko <askorichenko@netgate.com<mailto:askorichenko@netgate.com>>
Sent: Wednesday, July 3, 2024 3:14 AM
To: Long Li <longli@microsoft.com<mailto:longli@microsoft.com>>
Cc: stephen@networkplumber.org<mailto:stephen@networkplumber.org>; Sam Andrew <samandrew@microsoft.com<mailto:samandrew@microsoft.com>>; ferruh.yigit@amd.com<mailto:ferruh.yigit@amd.com>; andrew.rybchenko@oktetlabs.ru<mailto:andrew.rybchenko@oktetlabs.ru>; Wei Hu <weh@microsoft.com<mailto:weh@microsoft.com>>; dev@dpdk.org<mailto:dev@dpdk.org>
Subject: [EXTERNAL] Re: [PATCH] net/netvsc: fix mtu_set in netvsc devices
You don't often get email from askorichenko@netgate.com<mailto:askorichenko@netgate.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Thanks.
>> With this patch, do you see other problems with VPP?
No further problems were noticed and MTU can be set to custom values.
- Alexander Skorichenko
On Wed, Jul 3, 2024 at 2:35 AM Long Li <longli@microsoft.com<mailto:longli@microsoft.com>> wrote:
Thank you, Alexander.
The patch looks good to me. With this patch, do you see other problems with VPP?
I’d like to get a review from @Sam Andrew<mailto:samandrew@microsoft.com>.
Acked-by: Long Li <longli@microsoft.com<mailto:longli@microsoft.com>>
[-- Attachment #2: Type: text/html, Size: 7550 bytes --]
next prev parent reply other threads:[~2024-07-03 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 16:35 Alexander Skorichenko
2024-06-30 15:40 ` Stephen Hemminger
2024-07-02 8:49 ` Alexander Skorichenko
2024-07-03 0:35 ` Long Li
2024-07-03 10:13 ` Alexander Skorichenko
2024-07-03 22:50 ` [EXTERNAL] " Sam Andrew
2024-07-03 22:57 ` Long Li [this message]
2024-07-07 2:11 ` Ferruh Yigit
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=PH7PR21MB3071E7194453C932F594FB4ACEDD2@PH7PR21MB3071.namprd21.prod.outlook.com \
--to=longli@microsoft.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=askorichenko@netgate.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=samandrew@microsoft.com \
--cc=stephen@networkplumber.org \
--cc=weh@microsoft.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).