From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Rushil Gupta <rushilg@google.com>, Junfeng Guo <junfeng.guo@intel.com>
Cc: qi.z.zhang@intel.com, dev@dpdk.org, joshwash@google.com,
jeroendb@google.com
Subject: Re: [PATCH] doc: fix missing release note for GVE PMD DQO
Date: Tue, 4 Jul 2023 12:32:54 +0100 [thread overview]
Message-ID: <05464a13-818a-a44e-9af5-59296c7652e0@amd.com> (raw)
In-Reply-To: <CANzqiF7jbcomsUtXcbhZUyXQtsXX=MOEaw1QMPWEpaYYWo-t6w@mail.gmail.com>
On 7/3/2023 6:34 PM, Rushil Gupta wrote:
> On Sun, Jul 2, 2023 at 8:00 PM Junfeng Guo <junfeng.guo@intel.com> wrote:
>>
>> Add missing release note for GVE PMD enabling for DQO queue format.
>>
>> Fixes: a14d391c7d99 ("net/gve: add Tx queue setup for DQO")
>>
>> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
>> ---
>> doc/guides/rel_notes/release_23_07.rst | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/doc/guides/rel_notes/release_23_07.rst b/doc/guides/rel_notes/release_23_07.rst
>> index 4459144140..28c538acc9 100644
>> --- a/doc/guides/rel_notes/release_23_07.rst
>> +++ b/doc/guides/rel_notes/release_23_07.rst
>> @@ -200,6 +200,9 @@ New Features
>>
>> Enhanced the GRO library to support TCP packets over IPv6 network.
>>
>> +* **Added GVE PMD enabling for DQO.**
>> +
>> + Added GVE PMD enabling for DQO queue format.
>>
Updated as following while merging
* **Updated Google GVE net driver.**
Added DQO queue descriptor format support.
Also location was wrong, expected location of updates documented in
section comment, relocated according it.
Btw, what DQO stands for, I didn't able to find it?
>> Removed Items
>> -------------
>> --
>> 2.34.1
>>
> Acked-by: Rushil Gupta <rushilg@google.com>
>
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2023-07-04 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 3:00 Junfeng Guo
2023-07-03 17:34 ` Rushil Gupta
2023-07-04 11:32 ` Ferruh Yigit [this message]
2023-07-05 2:37 ` Guo, Junfeng
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=05464a13-818a-a44e-9af5-59296c7652e0@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=rushilg@google.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).