DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Guo, Junfeng" <junfeng.guo@intel.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	Rushil Gupta <rushilg@google.com>
Subject: RE: [PATCH 1/1] net/gve: update base code for DQO
Date: Wed, 12 Apr 2023 09:09:48 +0000	[thread overview]
Message-ID: <DM6PR11MB37234F84A8EFC221DC122E3DE79B9@DM6PR11MB3723.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2fa761ca-7b40-cf61-22cf-0078cf331f7d@amd.com>



> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@amd.com>
> Sent: Wednesday, April 12, 2023 16:50
> To: Guo, Junfeng <junfeng.guo@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>
> Cc: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Rushil Gupta
> <rushilg@google.com>
> Subject: Re: [PATCH 1/1] net/gve: update base code for DQO
> 
> On 4/11/2023 7:51 AM, Guo, Junfeng wrote:
> 
> Hi Junfeng, message moved down.
> 
> >
> >> -----Original Message-----
> >> From: Rushil Gupta <rushilg@google.com>
> >> Sent: Tuesday, April 11, 2023 12:59
> >> To: Zhang, Qi Z <qi.z.zhang@intel.com>; ferruh.yigit@amd.com
> >> Cc: Richardson, Bruce <bruce.richardson@intel.com>; dev@dpdk.org;
> >> Rushil Gupta <rushilg@google.com>; Guo, Junfeng
> >> <junfeng.guo@intel.com>
> >> Subject: [PATCH 1/1] net/gve: update base code for DQO
> >>
> >> Update gve base code to support DQO.
> >>
> >> This patch is based on this:
> >> https://patchwork.dpdk.org/project/dpdk/list/?series=27647&state=*
> >>
> >> Signed-off-by: Rushil Gupta <rushilg@google.com>
> >> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
> > Hi Ferruh & Bruce,
> >
> > This patch contains few lines change for the MIT licensed gve base code.
> > Note that there is no new files added, just some minor code update.
> >
> > Do we need to ask for special approval from the Tech Board for this?
> > Please help give some advice and also help review this patch. Thanks!
> >
> 
> Once the MIT license exception is in place, as far as I know no more
> approval is required per change.

Got it, thanks the comment!

Then we may also need your help to review, as well as the coming patch
set for GVE PMD enhancement for DPDK 23.07. Thanks in advance!

> 
> > BTW, Google will also help replace all the base code under MIT license
> > with the ones under BSD-3 license soon, which would make things more
> > easier.
> >
> 
> Is this different from base code under DPDK is changing license [1] ?
> 
> 
> [1]
> https://patches.dpdk.org/project/dpdk/list/?series=27570&state=%2A&ar
> chive=both
> 

The patch set of the above link only contains the processing of replace the
MIT licensed base code with the BSD-3 licensed base code. After some
discussion, we think Google is in the right place to do that work. And they
are working on that now.

This patch is mainly for the feature upstreaming of DPDK 23.07. It contains
only the code part, following previous license statements, without any
license change.

This patch is separated and sent by Google, to ensure there is no license
violation.

BTW, about the feature of GVE PMD enhancement, the rest code are all
about BSD-3 licensed files, and that patch set will be sent out soon.

Thanks!

  reply	other threads:[~2023-04-12  9:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11  4:59 [PATCH 0/1] *** Update drivers/net/gve/base code for DQO *** Rushil Gupta
2023-04-11  4:59 ` [PATCH 1/1] net/gve: update base code for DQO Rushil Gupta
2023-04-11  6:51   ` Guo, Junfeng
2023-04-12  8:50     ` Ferruh Yigit
2023-04-12  9:09       ` Guo, Junfeng [this message]
2023-04-12  9:34         ` Ferruh Yigit
2023-04-12  9:41           ` Guo, Junfeng
2023-04-12 15:42             ` Rushil Gupta
2023-04-12 16:02               ` Ferruh Yigit
2023-04-12 18:04                 ` Rushil Gupta
2023-04-14  5:17                   ` Rushil Gupta
2023-04-14 11:00                     ` Ferruh Yigit
2023-05-04  8:30   ` 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=DM6PR11MB37234F84A8EFC221DC122E3DE79B9@DM6PR11MB3723.namprd11.prod.outlook.com \
    --to=junfeng.guo@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.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).