All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Bradley M. Kuhn" <bkuhn@ebb.org>,
	Greg KH <gregkh@linuxfoundation.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, 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, 8 Jul 2021 12:37:46 -0700	[thread overview]
Message-ID: <20210708193746.7e2dbpgs33cl73wx@garbanzo> (raw)
In-Reply-To: <20210708150158.08ba548c@gandalf.local.home>

On Thu, Jul 08, 2021 at 03:01:58PM -0400, Steven Rostedt wrote:
> On Thu, 8 Jul 2021 10:52:54 -0700
> "Bradley M. Kuhn" <bkuhn@ebb.org> wrote:
> 
> > Joe Perches wrote:
> > >>> You can ask but it's the submitter's choice to license their code however
> > >>> they desire.  
> > 
> > … to which I'd add, as long as the license is GPLv2-only-compatible, which of
> > course (GPLv2-only|copyleft-next) is.
> 
> I agree with Joe on this, but I have to ask; What happens when someone
> makes a change to this file? The default kernel license is GPL-v2. Does this
> change automatically become the same as the file itself, or is the new
> change under the dual license?
> 
> I've made changes to code that had a dual license that wasn't GPL
> compatible, and the company involved asked me to sign off on the other
> license (which I did).

The Signed-off-by tag implies you are making a contribution under the
same license as the license file states. The more people are aware of
this fact, the better, and its then why we made DCO a public thing and
now other projects embrace it.

  Luis

  reply	other threads:[~2021-07-08 19:37 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
2021-07-08 17:52       ` Bradley M. Kuhn
2021-07-08 19:01         ` Steven Rostedt
2021-07-08 19:37           ` Luis Chamberlain [this message]
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=20210708193746.7e2dbpgs33cl73wx@garbanzo \
    --to=mcgrof@kernel.org \
    --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=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 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.