From: Greg KH <gregkh@linuxfoundation.org>
To: Tung Quang Nguyen <tung.quang.nguyen@est.tech>
Cc: Tim Bird <tim.bird@sony.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"tipc-discussion@lists.sourceforge.net"
<tipc-discussion@lists.sourceforge.net>,
"linux-spdx@vger.kernel.org" <linux-spdx@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jmaloy@redhat.com" <jmaloy@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>
Subject: Re: [PATCH] tipc: Add SPDX id lines to source files
Date: Fri, 5 Jun 2026 08:08:25 +0200 [thread overview]
Message-ID: <2026060546-unwitting-unvented-f6d4@gregkh> (raw)
In-Reply-To: <GV1P189MB1988FB0E53EA8D3FCC2533BDC6112@GV1P189MB1988.EURP189.PROD.OUTLOOK.COM>
On Fri, Jun 05, 2026 at 01:37:57AM +0000, Tung Quang Nguyen wrote:
> >Subject: [PATCH] tipc: Add SPDX id lines to source files
> >
> >Most of the tipc source files are missing SPDX-License-Identifier
> >lines. Add appropriate IDs to these files, and remove the
> >previous license lines from the headers. In this case,
> >every file received the 'GPL-2.0 OR BSD-3-Clause' ID expression.
>
> The original license of TIPC is GPL-2.0. Why do you think it should be dual licensing now ?
Because that is what the license text in these files say, or are you
stating that it is somehow incorrect and should not have been there at
all?
confused,
greg k-h
next prev parent reply other threads:[~2026-06-05 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 18:38 [PATCH] tipc: Add SPDX id lines to source files Tim Bird
2026-06-05 1:37 ` Tung Quang Nguyen
2026-06-05 6:08 ` Greg KH [this message]
2026-06-05 16:14 ` Bird, Tim
2026-06-05 16:35 ` Tung Quang Nguyen
2026-06-05 17:31 ` Bird, Tim
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=2026060546-unwitting-unvented-f6d4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tim.bird@sony.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.quang.nguyen@est.tech \
/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