DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] drivers: SPDX license id consistency
Date: Fri, 29 Mar 2019 00:15:38 +0100	[thread overview]
Message-ID: <1854596.sr6rv8kyS5@xps> (raw)
Message-ID: <20190328231538.0RpdhPS4ilDCBlg-elCbq-IFer_A96qAVyt7GPIQg8s@z> (raw)
In-Reply-To: <20190206222757.10835-1-stephen@networkplumber.org>

06/02/2019 23:27, Stephen Hemminger:
> All drivers should have SPDX on the first line of the source
> files in the format
>   /* SPDX-License-Identifier: ...
> 
> Several files used minor modifications which were inconsistent
> with the pattern. Fix it to make scanning tools easier.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  drivers/bus/fslmc/qbman/include/fsl_qbman_debug.h | 6 +++---
>  drivers/bus/fslmc/qbman/qbman_debug.c             | 5 ++---
>  drivers/crypto/dpaa2_sec/hw/desc/pdcp.h           | 4 +---
>  drivers/event/dpaa2/dpaa2_eventdev.h              | 7 ++-----
>  drivers/event/dpaa2/dpaa2_eventdev_logs.h         | 3 +--
>  drivers/mempool/dpaa2/dpaa2_hw_mempool_logs.h     | 3 +--
>  drivers/net/dpaa2/dpaa2_pmd_logs.h                | 3 +--
>  drivers/net/mvpp2/mrvl_mtr.c                      | 3 +--
>  8 files changed, 12 insertions(+), 22 deletions(-)

While at it, I'm removing multiple spaces in SPDX tags of fslmc.

Applied, thanks



  reply	other threads:[~2019-03-28 23:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 22:27 Stephen Hemminger
2019-03-28 23:15 ` Thomas Monjalon [this message]
2019-03-28 23:15   ` 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=1854596.sr6rv8kyS5@xps \
    --to=thomas@monjalon.net \
    --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).