From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Guo, Junfeng" <junfeng.guo@intel.com>,
Levend Sayar <levendsayar@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH 1/2] net/gve: change offloading capability
Date: Mon, 20 Feb 2023 15:43:40 +0000 [thread overview]
Message-ID: <45c7af33-c734-ba4a-f2ba-f5b52aa64419@amd.com> (raw)
In-Reply-To: <DM6PR11MB3723CD8197E6E5D61EA8C6CFE7A19@DM6PR11MB3723.namprd11.prod.outlook.com>
On 2/17/2023 9:11 AM, Guo, Junfeng wrote:
>
>
>> -----Original Message-----
>> From: Levend Sayar <levendsayar@gmail.com>
>> Sent: Friday, February 17, 2023 02:58
>> To: Guo, Junfeng <junfeng.guo@intel.com>
>> Cc: dev@dpdk.org; Levend Sayar <levendsayar@gmail.com>
>> Subject: [PATCH 1/2] net/gve: change offloading capability
>>
>> Google Virtual NIC is not doing IPv4 checksummimg.
>> Removed that capability from PMD.
>>
>> Signed-off-by: Levend Sayar <levendsayar@gmail.com>
>> ---
>
> Acked-by: Junfeng Guo <junfeng.guo@intel.com>
>
> Acked-by: Rushil Gupta <rushilg@google.com>
>
Fixes: a46583cf43c8 ("net/gve: support Rx/Tx")
Cc: stable@dpdk.org
Added Rushil's name to .mailmap while merging.
Patch 2/2 is not merged and it can progress independently.
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2023-02-20 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 18:58 Levend Sayar
2023-02-16 18:58 ` [PATCH 2/2] net/gve: add extended statistics Levend Sayar
2023-02-17 12:34 ` Ferruh Yigit
2023-02-19 0:26 ` Levend Sayar
2023-02-19 20:09 ` Ferruh Yigit
2023-02-19 20:37 ` Levend Sayar
2023-02-16 20:14 ` [PATCH 1/2] net/gve: change offloading capability Rushil Gupta
2023-02-17 9:07 ` Levend Sayar
2023-02-17 9:11 ` Guo, Junfeng
2023-02-17 9:15 ` Levend Sayar
2023-02-20 15:43 ` Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-10 13:05 Levend Sayar
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=45c7af33-c734-ba4a-f2ba-f5b52aa64419@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=junfeng.guo@intel.com \
--cc=levendsayar@gmail.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).