DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 0/4] Cleanup last remaining SPDX issues
Date: Tue, 16 Mar 2021 14:00:23 -0700	[thread overview]
Message-ID: <20210316210027.37213-1-stephen@networkplumber.org> (raw)

This resolves all the left over warnings and errors reported
by the check-spdx-tag script.

Stephen Hemminger (4):
  common/mlx5: add missing SPDX tag for windows headers
  devtools/check-spdx-tag.sh: ignore JSON files
  doc: add SPDX tag to custom CSS file
  app/test: remove license boilerplate

 app/test/test_timer_racecond.c              | 26 ---------------------
 devtools/check-spdx-tag.sh                  |  2 +-
 doc/guides/custom.css                       |  1 +
 drivers/common/mlx5/windows/mlx5_win_defs.h |  4 ++--
 drivers/common/mlx5/windows/mlx5_win_ext.h  |  4 ++--
 5 files changed, 6 insertions(+), 31 deletions(-)

-- 
2.30.2


             reply	other threads:[~2021-03-16 21:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 21:00 Stephen Hemminger [this message]
2021-03-16 21:00 ` [dpdk-dev] [PATCH 1/4] common/mlx5: add missing SPDX tag for windows headers Stephen Hemminger
2021-03-17  9:15   ` Tal Shnaiderman
2021-05-19  8:36     ` Thomas Monjalon
2021-03-16 21:00 ` [dpdk-dev] [PATCH 2/4] devtools/check-spdx-tag.sh: ignore JSON files Stephen Hemminger
2021-03-16 21:00 ` [dpdk-dev] [PATCH 3/4] doc: add SPDX tag to custom CSS file Stephen Hemminger
2021-05-19  8:44   ` Thomas Monjalon
2021-03-16 21:00 ` [dpdk-dev] [PATCH 4/4] app/test: remove license boilerplate Stephen Hemminger
2021-05-19  8:46 ` [dpdk-dev] [PATCH 0/4] Cleanup last remaining SPDX issues 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=20210316210027.37213-1-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).