From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 2/2] license: add MIT license exception for gve driver
Date: Wed, 19 Oct 2022 11:42:37 -0700 [thread overview]
Message-ID: <20221019184237.75506-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20221019184237.75506-1-stephen@networkplumber.org>
Tech Board and Governing Board approved license a exception
for new Google driver. More general approval for MIT
usage will be handled as needed.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
license/exceptions.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/license/exceptions.txt b/license/exceptions.txt
index 1bd4dbf8f780..e3862785eeb2 100644
--- a/license/exceptions.txt
+++ b/license/exceptions.txt
@@ -16,4 +16,5 @@ SPDX Identifier TB Approval Date GB Approval Date File name
2.BSD-2-Clause 10/23/2019 12/18/2019 lib/eal/windows/include/getopt.h
3.ISC AND
BSD-2-Clause 10/23/2019 12/18/2019 lib/eal/windows/getopt.c
+4. MIT 10/19/2022 10/18/2022 drivers/net/gve/base/*
---------------------------------------------------------------------------------------------------
--
2.35.1
next prev parent reply other threads:[~2022-10-19 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 16:32 [PATCH] license/README: fix pathnames and add MIT 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 ` [PATCH 1/2] license/README: fix pathnames and add MIT Hemant Agrawal
2022-10-18 3:10 ` 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 ` Stephen Hemminger [this message]
2022-10-27 10:28 ` [PATCH 2/2] license: add MIT license exception for gve driver 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=20221019184237.75506-2-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@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).