From: patchwork-bot+netdevbpf@kernel.org
To: Ronak Doshi <doshir@vmware.com>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
pv-drivers@vmware.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net 0/2] vmxnet3: couple of fixes
Date: Fri, 02 Dec 2022 10:40:16 +0000 [thread overview]
Message-ID: <166997761605.20046.4334047014624425550.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221130082148.9605-1-doshir@vmware.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 30 Nov 2022 00:21:45 -0800 you wrote:
> This series fixes following issues:
>
> Patch 1:
> This patch provides a fix to correctly report encapsulated LRO'ed
> packet.
>
> Patch 2:
> This patch provides a fix to use correct intrConf reference.
>
> [...]
Here is the summary with links:
- [v2,net,1/2] vmxnet3: correctly report encapsulated LRO packet
https://git.kernel.org/netdev/net/c/40b8c2a1af03
- [v2,net,2/2] vmxnet3: use correct intrConf reference when using extended queues
https://git.kernel.org/netdev/net/c/409e8ec8c582
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-12-02 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 8:21 [PATCH v2 net 0/2] vmxnet3: couple of fixes Ronak Doshi
2022-11-30 8:21 ` [PATCH v2 net 1/2] vmxnet3: correctly report encapsulated LRO packet Ronak Doshi
2022-11-30 8:21 ` [PATCH v2 net 2/2] vmxnet3: use correct intrConf reference when using extended queues Ronak Doshi
2022-11-30 8:22 ` kernel test robot
2022-12-02 10:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-05 22:42 [PATCH v2 net 0/2] vmxnet3: couple of fixes Ronak Doshi
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=166997761605.20046.4334047014624425550.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=doshir@vmware.com \
--cc=edumazet@google.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 \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.