public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Ronak Doshi <doshir@vmware.com>, <netdev@vger.kernel.org>
Cc: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 net 0/2] vmxnet3: couple of fixes
Date: Mon, 28 Nov 2022 15:52:24 -0800	[thread overview]
Message-ID: <67387f4f-5ece-fb9c-ae4a-2589cc7a34a5@intel.com> (raw)
In-Reply-To: <20221128195043.3914-1-doshir@vmware.com>



On 11/28/2022 11:50 AM, Ronak Doshi 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.
> 
> Changes in v1:
> - declare generic descriptor to be used
> 
> Ronak Doshi (2):
>    vmxnet3: correctly report encapsulated LRO packet
>    vmxnet3: use correct intrConf reference when using extended queues
> 
>   drivers/net/vmxnet3/vmxnet3_drv.c | 28 ++++++++++++++++++++++++----
>   1 file changed, 24 insertions(+), 4 deletions(-)
> 

It looks like you sent a bunch of versions rapidly, and you submitted an 
unversioned series followed by one with v1. That can make it difficult 
to track which is the most recent version and which one a reviewer 
should leave feedback on.

Typically it is assumed that the first submission is "v1" even if it 
doesn't include "v1" in its title. Thus your second submission would 
normally be "v2".

Thanks,
Jake

  reply	other threads:[~2022-11-28 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 19:50 [PATCH v1 net 0/2] vmxnet3: couple of fixes Ronak Doshi
2022-11-28 23:52 ` Jacob Keller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-28 19:32 Ronak Doshi
2022-11-28 19:31 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=67387f4f-5ece-fb9c-ae4a-2589cc7a34a5@intel.com \
    --to=jacob.e.keller@intel.com \
    --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