From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] SPDX check: files with missing or redundant license info
Date: Fri, 8 Nov 2019 14:23:42 +0000 [thread overview]
Message-ID: <20191108142342.GB1422@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20191107202849.3e776bfc@hermes.lan>
On Thu, Nov 07, 2019 at 08:28:49PM -0800, Stephen Hemminger wrote:
> Patches are outstanding for some of these.
> The big area with missing SPDX tags is all the ipsec-secgw shell scripts.
>
> No local changes to save
>
> Files without SPDX License
> --------------------------
>
<snip>
> usertools/dpdk-telemetry-client.py
>
This file looks to have a license tag, however, staring at it for 10
minutes finally reveals that there is a typo in it. Will send a patch to
fix.
/Bruce
prev parent reply other threads:[~2019-11-08 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 4:28 Stephen Hemminger
2019-11-08 14:23 ` Bruce Richardson [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=20191108142342.GB1422@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@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).