From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: RE: [PATCH 1/2] license/README: fix pathnames and add MIT
Date: Tue, 18 Oct 2022 02:46:40 +0000 [thread overview]
Message-ID: <AS8PR04MB9064FC3A9F880F2B46D043CD89289@AS8PR04MB9064.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20221018020437.412353-1-stephen@networkplumber.org>
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Tuesday, October 18, 2022 7:35 AM
> To: dev@dpdk.org
> Cc: techboard@dpdk.org; Stephen Hemminger
> <stephen@networkplumber.org>; Ferruh Yigit <ferruh.yigit@amd.com>
> Subject: [PATCH 1/2] license/README: fix pathnames and add MIT
>
> The pathnames in the license directory README are incorrect.
> The current repository puts license text in license/ not licenses/.
[Hemant] Can you break it into two parts:
1. for correcting the pathname - this can be merged asap.
2. adding MIT license - this need to wait till GB approval.
>
> Also, MIT license is used already in a couple of places so add the necessary
> entry in the README.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
> ---
> license/README | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/license/README b/license/README index
> 79dac86440a5..9def09058751 100644
> --- a/license/README
> +++ b/license/README
> @@ -58,7 +58,7 @@ DPDK Governing Board. Steps for any exception
> approval:
> 3. Technical Board then approach Governing Board for such limited approval
> for
> the given contribution only.
>
> -Any approvals shall be documented in "Licenses/exceptions.txt" with record
> +Any approvals shall be documented in "license/exceptions.txt" with
> +record
> dates.
>
> DPDK project supported licenses are:
> @@ -66,12 +66,16 @@ DPDK project supported licenses are:
> 1. BSD 3-clause "New" or "Revised" License
> SPDX-License-Identifier: BSD-3-Clause
> URL:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fspdx.o
> rg%2Flicenses%2FBSD-3-
> Clause%23licenseText&data=05%7C01%7Chemant.agrawal%40nxp.com
> %7Ca245eb56f1874d041fc808dab0ad1edb%7C686ea1d3bc2b4c6fa92cd99c5c
> 301635%7C0%7C0%7C638016554840767354%7CUnknown%7CTWFpbGZsb3d
> 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
> D%7C3000%7C%7C%7C&sdata=g%2FGcP4bwbyrE9SrnOzXfY7sWyOz8Dp
> dQt0avgbzbcS4%3D&reserved=0
> - DPDK License text: licenses/bsd-3-clause.txt
> + DPDK License text: license/bsd-3-clause.txt
> 2. GNU General Public License v2.0 only
> SPDX-License-Identifier: GPL-2.0
> URL:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fspdx.o
> rg%2Flicenses%2FGPL-
> 2.0.html%23licenseText&data=05%7C01%7Chemant.agrawal%40nxp.co
> m%7Ca245eb56f1874d041fc808dab0ad1edb%7C686ea1d3bc2b4c6fa92cd99c
> 5c301635%7C0%7C0%7C638016554840923577%7CUnknown%7CTWFpbGZsb
> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
> %3D%7C3000%7C%7C%7C&sdata=O34mh2TxnfW8sJ1XpsN3cr2RKqA9V
> AYbASBbnZCyhIQ%3D&reserved=0
> - DPDK License text: licenses/gpl-2.0.txt
> + DPDK License text: license/gpl-2.0.txt
> 3. GNU Lesser General Public License v2.1
> SPDX-License-Identifier: LGPL-2.1
> URL:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fspdx.o
> rg%2Flicenses%2FLGPL-
> 2.1.html%23licenseText&data=05%7C01%7Chemant.agrawal%40nxp.co
> m%7Ca245eb56f1874d041fc808dab0ad1edb%7C686ea1d3bc2b4c6fa92cd99c
> 5c301635%7C0%7C0%7C638016554840923577%7CUnknown%7CTWFpbGZsb
> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
> %3D%7C3000%7C%7C%7C&sdata=byXGbi21IodQwVzgDv0k%2BtbmEW
> o427UDWmzLI0fGwV8%3D&reserved=0
> - DPDK License text: licenses/lgpl-2.1.txt
> + DPDK License text: license/lgpl-2.1.txt 4. MIT License
> + SPDX-License-Identifier: MIT
> + URL:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fspdx.o
> rg%2Flicenses%2FMIT.html%23licenseText&data=05%7C01%7Chemant.
> agrawal%40nxp.com%7Ca245eb56f1874d041fc808dab0ad1edb%7C686ea1d3
> bc2b4c6fa92cd99c5c301635%7C0%7C0%7C638016554840923577%7CUnknow
> n%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1ha
> WwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=s4sKYVR0d8HjkTPki
> sFM3IZE9Zfi7lVA9qHCOanqUsY%3D&reserved=0
> + DPDK License text: license/mit.txt
> --
> 2.35.1
next prev parent reply other threads:[~2022-10-18 2:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 16:32 [PATCH] " Stephen Hemminger
2022-10-05 21:32 ` Ferruh Yigit
2022-10-18 2:04 ` [PATCH 1/2] " Stephen Hemminger
2022-10-18 2:04 ` [RFC 2/2] license: add using MIT license in base code Stephen Hemminger
2022-10-18 2:46 ` Hemant Agrawal [this message]
2022-10-18 3:10 ` [PATCH 1/2] license/README: fix pathnames and add MIT Stephen Hemminger
2022-10-18 7:38 ` Thomas Monjalon
2022-10-19 18:42 ` [PATCH 1/2] license/README: fix pathnames Stephen Hemminger
2022-10-19 18:42 ` [PATCH 2/2] license: add MIT license exception for gve driver Stephen Hemminger
2022-10-27 10:28 ` Thomas Monjalon
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=AS8PR04MB9064FC3A9F880F2B46D043CD89289@AS8PR04MB9064.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=stephen@networkplumber.org \
--cc=techboard@dpdk.org \
/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).