From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 0/2] standardize SPDX tag
Date: Thu, 05 Feb 2026 15:30:25 +0100 [thread overview]
Message-ID: <2888376.taCxCBeP46@thomas> (raw)
In-Reply-To: <aYRYW9PMGfu3NI_j@bricha3-mobl1.ger.corp.intel.com>
05/02/2026 09:44, Bruce Richardson:
> On Wed, Feb 04, 2026 at 09:46:04PM +0100, Thomas Monjalon wrote:
> > SPDX lines are fixed to be more standard,
> > and the checker is improved to detect some of the fixed issues.
> > For readability, the script changes are in a separate patch,
> > but for the sake of atomicity, the patches should be squashed.
> >
> > v2: update the script and README, and remove useless parentheses
> > v3: keep Linux uAPI imported file untouched
> >
> > Thomas Monjalon (2):
> > license: standardize SPDX tag
> > devtools: check SPDX syntax
> >
> Series-acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied
prev parent reply other threads:[~2026-02-05 14:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 9:13 [PATCH] license: standardize SPDX tag for 3-Clause BSD Thomas Monjalon
2025-11-12 9:31 ` Bruce Richardson
2025-11-12 9:38 ` Thomas Monjalon
2025-11-12 9:41 ` Bruce Richardson
2025-11-12 9:43 ` Thomas Monjalon
2026-01-14 6:00 ` Stephen Hemminger
2026-01-28 16:20 ` [PATCH v2] license: standardize SPDX tag Thomas Monjalon
2026-01-28 16:30 ` Bruce Richardson
2026-01-28 17:44 ` Thomas Monjalon
2026-01-28 17:46 ` Bruce Richardson
2026-02-04 20:46 ` [PATCH v3 0/2] " Thomas Monjalon
2026-02-04 20:46 ` [PATCH v3 1/2] license: " Thomas Monjalon
2026-02-05 5:34 ` Hemant Agrawal
2026-02-04 20:46 ` [PATCH v3 2/2] devtools: check SPDX syntax Thomas Monjalon
2026-02-05 1:41 ` [PATCH v3 0/2] standardize SPDX tag Stephen Hemminger
2026-02-05 8:44 ` Bruce Richardson
2026-02-05 14:30 ` Thomas Monjalon [this message]
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=2888376.taCxCBeP46@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.