From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Guo, Junfeng" <junfeng.guo@intel.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:50:06 +0100 [thread overview]
Message-ID: <2fa761ca-7b40-cf61-22cf-0078cf331f7d@amd.com> (raw)
In-Reply-To: <DM6PR11MB37232F81FAFE158854D5C531E79A9@DM6PR11MB3723.namprd11.prod.outlook.com>
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.
> 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&archive=both
next prev parent reply other threads:[~2023-04-12 8:51 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 [this message]
2023-04-12 9:09 ` Guo, Junfeng
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=2fa761ca-7b40-cf61-22cf-0078cf331f7d@amd.com \
--to=ferruh.yigit@amd.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.