From: patchwork-bot+netdevbpf@kernel.org
To: Ronak Doshi <doshir@vmware.com>
Cc: netdev@vger.kernel.org, pv-drivers@vmware.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, gyang@vmware.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] vmxnet3: disable overlay offloads if UPT device does not support
Date: Mon, 20 Jun 2022 08:20:27 +0000 [thread overview]
Message-ID: <165571322796.28545.7365793721968727456.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220620001014.27048-1-doshir@vmware.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 19 Jun 2022 17:10:13 -0700 you wrote:
> 'Commit 6f91f4ba046e ("vmxnet3: add support for capability registers")'
> added support for capability registers. These registers are used
> to advertize capabilities of the device.
>
> The patch updated the dev_caps to disable outer checksum offload if
> PTCR register does not support it. However, it missed to update
> other overlay offloads. This patch fixes this issue.
>
> [...]
Here is the summary with links:
- [net-next] vmxnet3: disable overlay offloads if UPT device does not support
https://git.kernel.org/netdev/net-next/c/a56b158a5078
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-06-20 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 0:10 [PATCH net-next] vmxnet3: disable overlay offloads if UPT device does not support Ronak Doshi
2022-06-20 8:20 ` patchwork-bot+netdevbpf [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=165571322796.28545.7365793721968727456.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=doshir@vmware.com \
--cc=edumazet@google.com \
--cc=gyang@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pv-drivers@vmware.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