DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Guo, Junfeng" <junfeng.guo@intel.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>, Rushil Gupta <rushilg@google.com>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"joshwash@google.com" <joshwash@google.com>,
	"jeroendb@google.com" <jeroendb@google.com>
Subject: RE: [PATCH] doc: fix missing release note for GVE PMD DQO
Date: Wed, 5 Jul 2023 02:37:30 +0000	[thread overview]
Message-ID: <DM6PR11MB3723635E9DA359AC285D07F5E72FA@DM6PR11MB3723.namprd11.prod.outlook.com> (raw)
In-Reply-To: <05464a13-818a-a44e-9af5-59296c7652e0@amd.com>



> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@amd.com>
> Sent: Tuesday, July 4, 2023 19:33
> To: Rushil Gupta <rushilg@google.com>; Guo, Junfeng
> <junfeng.guo@intel.com>
> Cc: Zhang, Qi Z <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
> 
> 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.

Thanks for the efforts!
We'll be careful about this in the following releases.
And put the doc and release note update align with the feature upstream.

> 
> 
> Btw, what DQO stands for, I didn't able to find it?

Yes, I also tried to find out but no meaningful explain. Maybe just a label.
https://github.com/GoogleCloudPlatform/compute-virtual-ethernet-linux/releases
"
v1.3.0
gve 1.3.0

This release adds support for gVNIC's Diorite queue format (DQO)
...
"
Thanks!

> 
> >>  Removed Items
> >>  -------------
> >> --
> >> 2.34.1
> >>
> > Acked-by: Rushil Gupta <rushilg@google.com>
> >
> 
> Applied to dpdk-next-net/main, thanks.
> 


      reply	other threads:[~2023-07-05  2:37 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
2023-07-05  2:37     ` Guo, Junfeng [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=DM6PR11MB3723635E9DA359AC285D07F5E72FA@DM6PR11MB3723.namprd11.prod.outlook.com \
    --to=junfeng.guo@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=jeroendb@google.com \
    --cc=joshwash@google.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).