From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/4] SPDX license tagging
Date: Fri, 23 Aug 2019 14:43:34 +0100 [thread overview]
Message-ID: <7abee9f6-a929-66bd-8c26-0215993235df@intel.com> (raw)
In-Reply-To: <20190815170223.12602-1-stephen@networkplumber.org>
On 8/15/2019 6:02 PM, Stephen Hemminger wrote:
> Remove redundant boilerplate on libraries I submitted.
> Add license id to map files.
Is licensing required for the .map file? They are just linker scripts with
function names, nothing more.
Is there anything negative can happen when they are missing license text?
>
> Stephen Hemminger (4):
> reciprocal: remove redundant boilerplate license text
> uuid: remove redundant BSD boilerplate
> drivers: add SPDX license id to map files
> lib: add SPDX license id to map files
<...>
prev parent reply other threads:[~2019-08-23 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 17:02 Stephen Hemminger
2019-08-15 17:02 ` [dpdk-dev] [PATCH 1/4] reciprocal: remove redundant boilerplate license text Stephen Hemminger
2019-08-15 17:02 ` [dpdk-dev] [PATCH 2/4] uuid: remove redundant BSD boilerplate Stephen Hemminger
2019-08-15 17:02 ` [dpdk-dev] [PATCH 3/4] drivers: add SPDX license id to map files Stephen Hemminger
2019-08-15 17:02 ` [dpdk-dev] [PATCH 4/4] lib: " Stephen Hemminger
2019-08-23 13:43 ` Ferruh Yigit [this message]
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=7abee9f6-a929-66bd-8c26-0215993235df@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).