From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
Cc: rushilg@google.com, joshwash@google.com, dev@dpdk.org,
Varun Lakkur Ambaji Rao <varun.la@gmail.com>
Subject: Re: [PATCH] net/gve: Add support for TSO in DQO RDA
Date: Thu, 8 Aug 2024 23:45:22 +0100 [thread overview]
Message-ID: <edda50f3-96e5-473d-a22f-c5f1996c5ada@amd.com> (raw)
In-Reply-To: <CA++LmPV8rHAyTQLjL3h8mq38N=1E08kwe+P=2GtFV6NdupyeSw@mail.gmail.com>
On 8/8/2024 7:25 PM, Tathagat Priyadarshi wrote:
>> Hi Tathagat,
>>
>> This patch has bits from other patch just merged, can you please send a
>> new version of this patch, on top of latest next-net [1] tree?
>>
>> [1]
>> https://git.dpdk.org/next/dpdk-next-net/
>
> Superseded via https://patches.dpdk.org/project/dpdk/patch/1723141392-2437012-1-git-send-email-tathagat.dpdk@gmail.com/
>
Thank you.
Instead of replying with this 'superseded' note, expectation is to send
next version, v2 in this case, send as a reply to previous version.
This way both versions will be in the same email thread, so it will be
more clear that old version is superseded. Also it will be in same email
thread in the mail list archive, so someone looking them later will be
able to see all versions history in same thread.
How to send new version as reply to previous one is documented in the
contribution guide, can you please check?
next prev parent reply other threads:[~2024-08-08 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 10:19 Tathagat Priyadarshi
2024-08-01 10:33 ` Tathagat Priyadarshi
2024-08-07 9:40 ` Ferruh Yigit
2024-08-08 18:25 ` Tathagat Priyadarshi
2024-08-08 22:45 ` Ferruh Yigit [this message]
2024-08-09 18:51 ` [PATCH v3] net/gve: add " Tathagat Priyadarshi
2024-08-19 10:03 ` Tathagat Priyadarshi
2024-08-27 3:11 ` Rushil Gupta
2024-08-27 14:04 ` Ferruh Yigit
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=edda50f3-96e5-473d-a22f-c5f1996c5ada@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=joshwash@google.com \
--cc=rushilg@google.com \
--cc=tathagat.dpdk@gmail.com \
--cc=varun.la@gmail.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).