patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <>
To: Thomas Monjalon <>,
	Hemant Agrawal <>,
	Stephen Hemminger <>
Cc: Ferruh Yigit <>,,
Subject: [dpdk-stable] [PATCH] license: fix typo
Date: Fri,  9 Apr 2021 16:53:56 +0100	[thread overview]
Message-ID: <> (raw)

Fixes: a4862c9e1a98 ("license: introduce SPDX identifiers")

Signed-off-by: Ferruh Yigit <>
 license/README | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/license/README b/license/README
index 874abaf4cd1e..79dac86440a5 100644
--- a/license/README
+++ b/license/README
@@ -49,7 +49,7 @@ with SPDX-License-Identifiers.
 Any exception to the DPDK IP policies shall be approved by DPDK Tech Board and
 DPDK Governing Board. Steps for any exception approval:
 1. Mention the appropriate license identifier form SPDX. If the license is not
-   listed in SPDX Licenses. It is the submitters responsibiliity to get it
+   listed in SPDX Licenses. It is the submitters responsibility to get it
    first listed.
 2. Get the required approval from the DPDK Technical Board. Technical Board may
    advise the author to check alternate means first. If no other alternative
@@ -72,6 +72,6 @@ DPDK project supported licenses are:
 	DPDK License text: licenses/gpl-2.0.txt
 3. GNU Lesser General Public License v2.1
-	SPDX-License-Identifieri: LGPL-2.1
+	SPDX-License-Identifier: LGPL-2.1
 	DPDK License text: licenses/lgpl-2.1.txt

             reply	other threads:[~2021-04-09 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 15:53 Ferruh Yigit [this message]
2021-04-09 16:19 ` Stephen Hemminger
2021-04-09 16:49   ` [dpdk-stable] [dpdk-dev] " Hemant Agrawal
2021-04-13 10:47     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).