DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] SPDX license tag nag
Date: Fri, 29 Nov 2019 09:45:21 -0800	[thread overview]
Message-ID: <20191129094521.702d5990@hermes.lan> (raw)

This is the current status of DPDK 19.11 about files with missing or incorrect SPDX
tags. This is a polite nag, please either ack the patches, or merge them.
If there is no patch please submit one if you are the author.

Several patches are outstanding to fix some of these. But others have not
been addressed.

Pending:
https://patchwork.dpdk.org/patch/59769/
	lib/librte_ethdev/rte_ethdev_pci.h
	lib/librte_ethdev/rte_ethdev_vdev.h
https://patchwork.dpdk.org/patch/59770/
	app/test-pmd/flowgen.c
	app/test-pmd/macswap.c
https://patchwork.dpdk.org/patch/59771/
	app/test/test_compressdev_test_buffer.h
https://patchwork.dpdk.org/patch/62802/
	examples/performance-thread/l3fwd-thread/test.sh


Patches needed:
app/test/test_timer_racecond.c
devtools/cocci.sh
devtools/load-devel-config
examples/ipsec-secgw/test/trs_aesgcm_inline_crypto_fallback_defs.sh
examples/ipsec-secgw/test/tun_aesgcm_inline_crypto_fallback_defs.sh

The nagging will continue until all files are fixed.

                 reply	other threads:[~2019-11-29 17:45 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=20191129094521.702d5990@hermes.lan \
    --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).