netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/8] vmxnet3: upgrade to version 7
Date: Thu, 09 Jun 2022 11:10:14 +0000	[thread overview]
Message-ID: <165477301463.8270.15863308665525214047.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220608032353.964-1-doshir@vmware.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 7 Jun 2022 20:23:45 -0700 you wrote:
> vmxnet3 emulation has recently added several new features including
> support for uniform passthrough(UPT). To make UPT work vmxnet3 has
> to be enhanced as per the new specification. This patch series
> extends the vmxnet3 driver to leverage these new features.
> 
> Compatibility is maintained using existing vmxnet3 versioning mechanism as
> follows:
>  - new features added to vmxnet3 emulation are associated with new vmxnet3
>    version viz. vmxnet3 version 7.
>  - emulation advertises all the versions it supports to the driver.
>  - during initialization, vmxnet3 driver picks the highest version number
>  supported by both the emulation and the driver and configures emulation
>  to run at that version.
> 
> [...]

Here is the summary with links:
  - [v3,net-next,1/8] vmxnet3: prepare for version 7 changes
    https://git.kernel.org/netdev/net-next/c/55f0395fcace
  - [v3,net-next,2/8] vmxnet3: add support for capability registers
    https://git.kernel.org/netdev/net-next/c/6f91f4ba046e
  - [v3,net-next,3/8] vmxnet3: add support for large passthrough BAR register
    https://git.kernel.org/netdev/net-next/c/543fb6740541
  - [v3,net-next,4/8] vmxnet3: add support for out of order rx completion
    https://git.kernel.org/netdev/net-next/c/2c5a5748105a
  - [v3,net-next,5/8] vmxnet3: add command to set ring buffer sizes
    (no matching commit)
  - [v3,net-next,6/8] vmxnet3: limit number of TXDs used for TSO packet
    https://git.kernel.org/netdev/net-next/c/d2857b99a74b
  - [v3,net-next,7/8] vmxnet3: use ext1 field to indicate encapsulated packet
    https://git.kernel.org/netdev/net-next/c/60cafa0395c2
  - [v3,net-next,8/8] vmxnet3: update to version 7
    https://git.kernel.org/netdev/net-next/c/acc38e041bd3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-06-09 11:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  3:23 [PATCH v3 net-next 0/8] vmxnet3: upgrade to version 7 Ronak Doshi
2022-06-08  3:23 ` [PATCH v3 net-next 1/8] vmxnet3: prepare for version 7 changes Ronak Doshi
2022-06-08  3:23 ` [PATCH v3 net-next 2/8] vmxnet3: add support for capability registers Ronak Doshi
2022-06-08  3:23 ` [PATCH v3 net-next 3/8] vmxnet3: add support for large passthrough BAR register Ronak Doshi
2022-06-08  3:23 ` [PATCH v3 net-next 4/8] vmxnet3: add support for out of order rx completion Ronak Doshi
2022-06-08  3:23 ` [PATCH v3 net-next 5/8] vmxnet3: add command to set ring buffer sizes Ronak Doshi
2022-06-08  3:23 ` [PATCH v3 net-next 6/8] vmxnet3: limit number of TXDs used for TSO packet Ronak Doshi
2022-06-08  3:23 ` [PATCH v3 net-next 7/8] vmxnet3: use ext1 field to indicate encapsulated packet Ronak Doshi
2022-06-08  3:23 ` [PATCH v3 net-next 8/8] vmxnet3: update to version 7 Ronak Doshi
2022-06-09 11:10 ` 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=165477301463.8270.15863308665525214047.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 \
    /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).