From: "Guo, Junfeng" <junfeng.guo@intel.com>
To: Ferruh Yigit <ferruh.yigit@amd.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 v3 1/3] net/gve: switch license from MIT to BSD-3
Date: Wed, 29 Mar 2023 02:35:22 +0000 [thread overview]
Message-ID: <DM6PR11MB3723668798C756753B260ED3E7899@DM6PR11MB3723.namprd11.prod.outlook.com> (raw)
In-Reply-To: <c5919f18-36b3-ec32-f281-916ff8c960a7@amd.com>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@amd.com>
> Sent: Tuesday, March 28, 2023 18:36
> 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 v3 1/3] net/gve: switch license from MIT to BSD-3
>
> On 3/28/2023 10:45 AM, Junfeng Guo wrote:
> > diff --git a/drivers/net/gve/base/gve_osdep.h
> b/drivers/net/gve/base/gve_osdep.h
> > index 7cb73002f4..f7d87fec16 100644
> > --- a/drivers/net/gve/base/gve_osdep.h
> > +++ b/drivers/net/gve/base/gve_osdep.h
> > @@ -1,5 +1,5 @@
> > /* SPDX-License-Identifier: BSD-3-Clause
> > - * Copyright(C) 2022 Intel Corporation
> > + * Copyright (c) 2022-2023 Google LLC
> > */
>
> Is this intentional to move Copyright from Intel to Google?
Oh, sorry! This is updated by mistake.
In tradition, the osdep.h file is in Intel's copyright with
BSD-3 License. So it should not be included in the patch
as no License update for this file.
I'll fix this and put this change into 2nd one of patch set.
Thanks for the careful review!
next prev parent reply other threads:[~2023-03-29 2:35 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
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 [this message]
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=DM6PR11MB3723668798C756753B260ED3E7899@DM6PR11MB3723.namprd11.prod.outlook.com \
--to=junfeng.guo@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jeroendb@google.com \
--cc=jingjing.wu@intel.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).