DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "techboard@dpdk.org" <techboard@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] SPDX compliance for the 19.11 release
Date: Fri, 22 Nov 2019 10:07:22 +0000	[thread overview]
Message-ID: <VI1PR0401MB254145D09A32F3FD94744F6689490@VI1PR0401MB2541.eurprd04.prod.outlook.com> (raw)

Hi all,
          Though large portion of DPDK code/scripts are now using SPDX license tags, there are still some old files having full license text without SPDX tags.  Their original authors/copyright holders are either not responding or not traceable.

Let's not wait for them forever.  Following patch just add the SPDX tags without removing the original license plate.

http://patchwork.dpdk.org/patch/63225/  "add top level SPDX license identifier."

Please review and ack it.

Also, following related patches are ready for merge.  (they are acked or submitted by the copyright holders)


  1.  https://patches.dpdk.org/patch/57613/ "app/test_thash: replace license text with SPDX tag"
  2.  http://patchwork.dpdk.org/patch/62801/  "examples/l2fwd-event: add missing SPDX license header"
  3.  https://patchwork.dpdk.org/patch/62804/     "devtools: add SPDX license tag check script"


Finally, following patch is still waiting the Governing Board exception approval:
http://patchwork.dpdk.org/patch/59976/  "[v2] pmdinfogen: add SPDX license tag"

Regards,
Hemant



                 reply	other threads:[~2019-11-22 10:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=VI1PR0401MB254145D09A32F3FD94744F6689490@VI1PR0401MB2541.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=dev@dpdk.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).