DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
	Sachin Saxena <sachin.saxena@nxp.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH] license: standardize SPDX tag for 3-Clause BSD
Date: Wed, 12 Nov 2025 10:43:16 +0100	[thread overview]
Message-ID: <3883425.DVCPrJfaZc@thomas> (raw)
In-Reply-To: <aRRWWdQjWTodkYxG@bricha3-mobl1.ger.corp.intel.com>

12/11/2025 10:41, Bruce Richardson:
> On Wed, Nov 12, 2025 at 10:38:44AM +0100, Thomas Monjalon wrote:
> > 12/11/2025 10:31, Bruce Richardson:
> > > On Wed, Nov 12, 2025 at 10:13:35AM +0100, Thomas Monjalon wrote:
> > > > Make sure the SPDX tag is used as defined in license/README.
> > > > Reduce separator to single space.
> > > > Use parenthesis and uppercased "OR" when a second license is applied.
> > > 
> > > Upper-case or is fine, I suppose, but I'm not convinced we need the
> > > parentheses. However, I see other drivers tend to have it, so let's
> > > standardize on that.
> > 
> > I'm not convinced as well.
> > 
> > Looking at https://spdx.dev/learn/handling-license-info/
> > it seems we don't need parentheses in general.
> > 
> Shall we just avoid fixing the parens until we definitively decide on that.
> Just standardize on spacing and upper case "OR"? Whatever approach you
> decide for this release, you can keep my ack.

I plan to rework this patch by standardizing without parentheses,
and add more checks.



      reply	other threads:[~2025-11-12  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12  9:13 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 [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=3883425.DVCPrJfaZc@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=sachin.saxena@nxp.com \
    --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).