From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v5] devtools: add new SPDX license compliance checker
Date: Fri, 31 Jul 2020 00:00:27 +0200 [thread overview]
Message-ID: <4113141.RHlPbOjEBA@thomas> (raw)
In-Reply-To: <20200714162558.0b80575c@hermes.lan>
15/07/2020 01:25, Stephen Hemminger:
> On Tue, 14 Jul 2020 16:21:01 -0700
> Stephen Hemminger <stephen@networkplumber.org> wrote:
>
> > Simple script to look for drivers and scripts that
> > are missing requires SPDX header.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Preprocessor Directives
>
> Because of the long delay in merging this tool new
> files have come in that are not following the required guidelines!
Probably it would have helped if you Cc'ed some persons known to be
interested in this topic. Getting reviews is harder recently.
next prev parent reply other threads:[~2020-07-30 22:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 15:59 [dpdk-dev] [PATCH v2] " Stephen Hemminger
2020-02-07 17:39 ` Stephen Hemminger
2020-02-07 17:52 ` [dpdk-dev] [PATCH v3] " Stephen Hemminger
2020-02-22 15:43 ` Thomas Monjalon
2020-02-22 15:45 ` Thomas Monjalon
2020-02-24 21:01 ` [dpdk-dev] [PATCH v4] " Stephen Hemminger
2020-04-28 20:15 ` Stephen Hemminger
2020-06-11 18:46 ` Stephen Hemminger
2020-06-11 21:32 ` Thomas Monjalon
2020-06-11 21:39 ` Thomas Monjalon
2020-06-12 8:36 ` Gaëtan Rivet
2020-06-12 14:53 ` Stephen Hemminger
2020-06-12 15:42 ` Thomas Monjalon
2020-06-12 9:05 ` Gaëtan Rivet
2020-07-14 23:23 ` Stephen Hemminger
2020-02-26 1:14 ` [dpdk-dev] [PATCH] " Stephen Hemminger
2020-07-14 23:21 ` [dpdk-dev] [PATCH v5] " Stephen Hemminger
2020-07-14 23:25 ` Stephen Hemminger
2020-07-30 22:00 ` Thomas Monjalon [this message]
2020-07-23 4:36 ` Stephen Hemminger
2020-07-30 22:06 ` Thomas Monjalon
2020-07-30 23:41 ` Stephen Hemminger
2020-08-26 15:12 ` Stephen Hemminger
2020-08-26 15:43 ` Bruce Richardson
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=4113141.RHlPbOjEBA@thomas \
--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).