netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ronak Doshi <ronak.doshi@broadcom.com>
Cc: netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/4] vmxnet3: upgrade to version 9
Date: Wed, 05 Jun 2024 23:00:34 +0000	[thread overview]
Message-ID: <171762843408.9199.15628895489607695720.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240531193050.4132-1-ronak.doshi@broadcom.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 31 May 2024 12:30:45 -0700 you wrote:
> vmxnet3 emulation has recently added timestamping feature which allows the
> hypervisor (ESXi) to calculate latency from guest virtual NIC driver to all
> the way up to the physical NIC. This patch series extends vmxnet3 driver
> to leverage these new feature.
> 
> 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 9.
> - 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:
  - [v2,net-next,1/4] vmxnet3: prepare for version 9 changes
    https://git.kernel.org/netdev/net-next/c/4978478a6888
  - [v2,net-next,2/4] vmxnet3: add latency measurement support in vmxnet3
    https://git.kernel.org/netdev/net-next/c/4c22fad70256
  - [v2,net-next,3/4] vmxnet3: add command to allow disabling of offloads
    https://git.kernel.org/netdev/net-next/c/2e5010fd0c43
  - [v2,net-next,4/4] vmxnet3: update to version 9
    https://git.kernel.org/netdev/net-next/c/63587234d42a

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



      parent reply	other threads:[~2024-06-05 23:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 19:30 [PATCH v2 net-next 0/4] vmxnet3: upgrade to version 9 Ronak Doshi
2024-05-31 19:30 ` [PATCH v2 net-next 1/4] vmxnet3: prepare for version 9 changes Ronak Doshi
2024-06-05 13:49   ` Simon Horman
2024-05-31 19:30 ` [PATCH v2 net-next 2/4] vmxnet3: add latency measurement support in vmxnet3 Ronak Doshi
2024-06-05 13:51   ` Simon Horman
2024-05-31 19:30 ` [PATCH v2 net-next 3/4] vmxnet3: add command to allow disabling of offloads Ronak Doshi
2024-06-05 13:52   ` Simon Horman
2024-05-31 19:30 ` [PATCH v2 net-next 4/4] vmxnet3: update to version 9 Ronak Doshi
2024-06-05 13:52   ` Simon Horman
2024-06-01 23:05 ` [PATCH v2 net-next 0/4] vmxnet3: upgrade " Jakub Kicinski
2024-06-05 23:00 ` 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=171762843408.9199.15628895489607695720.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ronak.doshi@broadcom.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).