From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>, "Bradley M. Kuhn" <bkuhn@ebb.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
tglx@linutronix.de, akpm@linux-foundation.org, shuah@kernel.org,
rafael@kernel.org, rgoldwyn@suse.com, kuno@frob.nl,
fontana@sharpeleven.org, Ciaran.Farrell@suse.com,
Christopher.DeNicolo@suse.com, hch@lst.de, corbet@lwn.net,
linux@leemhuis.info, ast@kernel.org, andriin@fb.com,
daniel@iogearbox.net, atenart@kernel.org, alobakin@pm.me,
weiwan@google.com, ap420073@gmail.com, tj@kernel.org,
jeyu@kernel.org, ngupta@vflare.org,
sergey.senozhatsky.work@gmail.com, minchan@kernel.org,
axboe@kernel.dk, mbenes@suse.com, jpoimboe@redhat.com,
keescook@chromium.org, jikos@kernel.org, rostedt@goodmis.org,
peterz@infradead.org, linux-block@vger.kernel.org,
linux-spdx@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
copyleft-next@lists.fedorahosted.org
Subject: Re: [PATCH 0/2] LICENSES: add and use copyleft-next-0.3.1
Date: Thu, 08 Jul 2021 09:56:05 -0700 [thread overview]
Message-ID: <d538c07ccb0176fe7c715bf4cb3b48d84b378c52.camel@perches.com> (raw)
In-Reply-To: <YOcakETswyEN58j6@kroah.com>
On Thu, 2021-07-08 at 17:32 +0200, Greg KH wrote:
> On Thu, Jul 08, 2021 at 07:59:13AM -0700, Bradley M. Kuhn wrote:
> > Greg KH wrote:
> > > Any chance you wish to just change the license of these files, given that
> > > you are the only one that has tried to use it for kernel code?
> >
> > There is a lot of dual-licensed (GPLv2-only|{2,3}-Clause-BSD) code already in
> > Linux. Many corporate copyright holders have well documented strong reasons
> > for wanting that. (Those policy goals and the analysis behind them, I find
> > problematic and sometimes outright wrong, but nonetheless it's their right to
> > license their copyrights that way, and the license *is* GPLv2-only
> > compatible, as is Luis'!).
> >
> > I assume that you're not asking those companies to relicense to pure
> > GPLv2-only.
>
> On the contrary, I have stated in public many times to companies that
> try to add dual-licensed new kernel code that they should only do so if
> they provide a really good reason, and pushed back on them numerous
> times. See the mailing list archives for details if you care.
>
> So yes, I am asking them, this is not anything new.
>
> Let's keep it simple please, and not add new licenses for no real good
> reason if at all possible.
You can ask but it's the submitter's choice to license their code
however they desire.
next prev parent reply other threads:[~2021-07-08 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 18:43 [PATCH 0/2] LICENSES: add and use copyleft-next-0.3.1 Luis Chamberlain
2021-07-07 18:43 ` [PATCH 1/2] LICENSES: Add the copyleft-next-0.3.1 license Luis Chamberlain
2021-07-07 18:43 ` [PATCH 2/2] testing: use the copyleft-next-0.3.1 SPDX tag Luis Chamberlain
2021-07-08 4:14 ` [PATCH 0/2] LICENSES: add and use copyleft-next-0.3.1 Christoph Hellwig
2021-07-08 19:00 ` Luis Chamberlain
2021-07-08 6:22 ` Greg KH
2021-07-08 14:59 ` Bradley M. Kuhn
2021-07-08 15:32 ` Greg KH
2021-07-08 16:56 ` Joe Perches [this message]
2021-07-08 17:52 ` Bradley M. Kuhn
2021-07-08 19:01 ` Steven Rostedt
2021-07-08 19:37 ` Luis Chamberlain
2021-07-08 20:08 ` Steven Rostedt
2021-07-08 17:08 ` Tim.Bird
2021-07-08 19:33 ` Luis Chamberlain
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=d538c07ccb0176fe7c715bf4cb3b48d84b378c52.camel@perches.com \
--to=joe@perches.com \
--cc=Christopher.DeNicolo@suse.com \
--cc=Ciaran.Farrell@suse.com \
--cc=akpm@linux-foundation.org \
--cc=alobakin@pm.me \
--cc=andriin@fb.com \
--cc=ap420073@gmail.com \
--cc=ast@kernel.org \
--cc=atenart@kernel.org \
--cc=axboe@kernel.dk \
--cc=bkuhn@ebb.org \
--cc=copyleft-next@lists.fedorahosted.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=fontana@sharpeleven.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=kuno@frob.nl \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mbenes@suse.com \
--cc=mcgrof@kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=weiwan@google.com \
/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).