DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Guo, Junfeng" <junfeng.guo@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Rushil Gupta <rushilg@google.com>,
	Joshua Washington <joshwash@google.com>,
	Jeroen de Borst <jeroendb@google.com>
Subject: Re: [PATCH 2/2] net/gve: update copyright holders
Date: Tue, 28 Mar 2023 11:10:00 +0100	[thread overview]
Message-ID: <dbf38348-7f0e-8575-676a-f50481336f52@amd.com> (raw)
In-Reply-To: <DM6PR11MB372357CB236F0156F823434EE7889@DM6PR11MB3723.namprd11.prod.outlook.com>

On 3/28/2023 10:35 AM, Guo, Junfeng wrote:
> 
> 
>> -----Original Message-----
>> From: Ferruh Yigit <ferruh.yigit@amd.com>
>> Sent: Tuesday, March 28, 2023 16:57
>> To: Guo, Junfeng <junfeng.guo@intel.com>; Zhang, Qi Z
>> <qi.z.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>; Xing,
>> Beilei <beilei.xing@intel.com>
>> Cc: dev@dpdk.org; Rushil Gupta <rushilg@google.com>; Joshua
>> Washington <joshwash@google.com>; Jeroen de Borst
>> <jeroendb@google.com>
>> Subject: Re: [PATCH 2/2] net/gve: update copyright holders
>>
>> On 3/28/2023 3:08 AM, Junfeng Guo wrote:
>>> Add Google LLC as one of the copyright holders for GVE.
>>>
>>> Signed-off-by: Rushil Gupta <rushilg@google.com>
>>> Signed-off-by: Joshua Washington <joshwash@google.com>
>>> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
>>> Signed-off-by: Jeroen de Borst <jeroendb@google.com>
>>> ---
>>>  drivers/net/gve/gve_ethdev.c | 32
>> ++++++++++++++++++++++++++++++--
>>>  drivers/net/gve/gve_ethdev.h | 32
>> ++++++++++++++++++++++++++++++--
>>>  drivers/net/gve/gve_logs.h   | 32 ++++++++++++++++++++++++++++++-
>> -
>>>  drivers/net/gve/gve_rx.c     | 32 ++++++++++++++++++++++++++++++--
>>>  drivers/net/gve/gve_tx.c     | 32 ++++++++++++++++++++++++++++++--
>>>  drivers/net/gve/meson.build  | 31
>> ++++++++++++++++++++++++++++++-
>>>  6 files changed, 180 insertions(+), 11 deletions(-)
>>>
>>> diff --git a/drivers/net/gve/gve_ethdev.c
>> b/drivers/net/gve/gve_ethdev.c
>>> index cf28a4a3b7..1b8f0fde8f 100644
>>> --- a/drivers/net/gve/gve_ethdev.c
>>> +++ b/drivers/net/gve/gve_ethdev.c
>>> @@ -1,5 +1,33 @@
>>> -/* SPDX-License-Identifier: BSD-3-Clause
>>> - * Copyright(C) 2022 Intel Corporation
>>> +/*
>>> + * SPDX-License-Identifier: BSD-3-Clause
>>> + *
>>> + * Copyright (c) 2022-2023 Google LLC
>>> + * Copyright (c) 2022-2023 Intel Corporation
>>> + *
>>> + * Redistribution and use in source and binary forms, with or without
>> modification,
>>> + * are permitted provided that the following conditions are met:
>>> + *
>>> + * 1. Redistributions of source code must retain the above copyright
>> notice, this
>>> + *    list of conditions and the following disclaimer.
>>> + *
>>> + * 2. Redistributions in binary form must reproduce the above
>> copyright notice,
>>> + *    this list of conditions and the following disclaimer in the
>> documentation
>>> + *    and/or other materials provided with the distribution.
>>> + *
>>> + * 3. Neither the name of the copyright holder nor the names of its
>> contributors
>>> + *    may be used to endorse or promote products derived from this
>> software without
>>> + *    specific prior written permission.
>>> + *
>>> + * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
>> CONTRIBUTORS "AS IS" AND
>>> + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>> LIMITED TO, THE IMPLIED
>>> + * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
>> PARTICULAR PURPOSE ARE
>>> + * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
>> CONTRIBUTORS BE LIABLE FOR
>>> + * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
>> CONSEQUENTIAL DAMAGES
>>> + * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
>> SUBSTITUTE GOODS OR SERVICES;
>>> + * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
>> HOWEVER CAUSED AND ON
>>> + * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
>> LIABILITY, OR TORT
>>> + * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
>> OUT OF THE USE OF THIS
>>> + * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
>> DAMAGE.
>>>   */
>>
>> Can you please separate the patches that updates license and copyright?
> 
> Sure.
> 
> The background is that, in the past (DPDK 22.11) we didn't get the approval
> of license from Google, thus chose the MIT License for the base code, and 
> BSD-3 License for GVE common code (without the files in /base folder).
> We also left the copyright holder of base code just to Google Inc, and made
> Intel as the copyright holder of GVE common code (without /base folder).
> 
> Today we are working together for GVE dev and maintaining. And we got
> the approval of BSD-3 License from Google for the base code.
> Thus we dicided to 1) switch the License of GVE base code from MIT to BSD-3;
> 2) add Google LLC as one of the copyright holders for GVE common code.
> 

+1 to switch the DPDK common BSD-3 license, instead of having an
exception for the driver, it simplifies things.

Thank you for following this up.


  reply	other threads:[~2023-03-28 10:10 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  2:08 [PATCH 0/2] update license and copyright Junfeng Guo
2023-03-28  2:08 ` [PATCH 1/2] net/gve: switch copyright from MIT to BSD-3 Junfeng Guo
2023-03-28  8:51   ` Ferruh Yigit
2023-03-28  8:57     ` Guo, Junfeng
2023-03-28  8:55   ` Ferruh Yigit
2023-03-28  9:06     ` Guo, Junfeng
2023-03-28  9:09       ` Ferruh Yigit
2023-03-28  9:35         ` Guo, Junfeng
2023-03-28  2:08 ` [PATCH 2/2] net/gve: update copyright holders Junfeng Guo
2023-03-28  8:56   ` Ferruh Yigit
2023-03-28  9:35     ` Guo, Junfeng
2023-03-28 10:10       ` Ferruh Yigit [this message]
2023-03-29 14:07       ` Thomas Monjalon
2023-03-30  7:20         ` Guo, Junfeng
2023-03-30 13:14           ` Thomas Monjalon
2023-03-30 15:18             ` Rushil Gupta
2023-03-30 15:26             ` Rushil Gupta
2023-03-31  2:32             ` Guo, Junfeng
2023-03-28  9:28 ` [PATCH v2 0/3] update license and " Junfeng Guo
2023-03-28  9:28   ` [PATCH v2 1/3] net/gve: switch license from MIT to BSD-3 Junfeng Guo
2023-03-28  9:28   ` [PATCH v2 2/3] net/gve: update copyright holders Junfeng Guo
2023-03-28  9:28   ` [PATCH v2 3/3] net/gve: add maintainers for GVE Junfeng Guo
2023-03-28  9:45   ` [PATCH v3 0/3] update license and copyright holders Junfeng Guo
2023-03-28  9:45     ` [PATCH v3 1/3] net/gve: switch license from MIT to BSD-3 Junfeng Guo
2023-03-28 10:36       ` Ferruh Yigit
2023-03-29  2:35         ` Guo, Junfeng
2023-03-28  9:45     ` [PATCH v3 2/3] net/gve: update copyright holders Junfeng Guo
2023-03-28 10:37       ` Ferruh Yigit
2023-03-28 22:11         ` Rushil Gupta
2023-03-28  9:45     ` [PATCH v3 3/3] net/gve: add maintainers for GVE Junfeng Guo
2023-03-28 10:00       ` Guo, Junfeng
2023-03-28 10:34         ` Ferruh Yigit
2023-03-29  2:54           ` Guo, Junfeng
2023-03-29  2:26     ` [PATCH v4 0/3] update license and copyright holders Junfeng Guo
2023-03-29  2:27       ` [PATCH v4 1/3] net/gve: switch license from MIT to BSD-3 Junfeng Guo
2023-03-29  8:08         ` Ferruh Yigit
2023-03-29  2:27       ` [PATCH v4 2/3] net/gve: update copyright holders Junfeng Guo
2023-03-29  2:27       ` [PATCH v4 3/3] net/gve: add maintainers for GVE Junfeng Guo

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=dbf38348-7f0e-8575-676a-f50481336f52@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jeroendb@google.com \
    --cc=jingjing.wu@intel.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).