mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
	Oleksij Rempel <linux@rempel-privat.de>,
	barebox@lists.infradead.org
Subject: Re: [PATCH v1 1/3] MIPS: migrate all files to SPDX
Date: Tue, 18 Dec 2018 11:52:54 +0100	[thread overview]
Message-ID: <20181218105254.jsaewf5glubqh4wt@pengutronix.de> (raw)
In-Reply-To: <20181218123250.5a76fa37a9ceba65dd68fff9@gmail.com>

On Tue, Dec 18, 2018 at 12:32:50PM +0300, Antony Pavlov wrote:
> > Beside, go you agree to upgrade files copyrighted by you as 
> > GPL-2.0-or-later?
> 
> Not now. We use many codes from linux kernel (mostly GPL-2.0-only).
> Can we face the problems of porting linux kernel code to barebox?
> 
> I see strange thing: most barebox files are GPL-2.0-only,
> but asm/bitopts.h changed GPL-2.0-only to GPL-2.0-or-later after the commit
> 
> commit 227a20fe31c6a03795a202f95af95fb371951963
> Author: Sascha Hauer <s.hauer@pengutronix.de>
> Date:   Wed Jul 16 09:40:30 2014 +0200
> 
>     consistently use the same bitops.h file
> 
> @Sascha Please comment on GPL-2.0-only vs GPL-2.0-or-later in barebox.

Barebox has preferred GPL-2.0-only starting from day-1, see toplevel
COPYING. As GPL-2.0-or-later is compatible with that, it is ok to
include or-later code into an otherwhise-2.0-only codebase.

rsc
-- 
Pengutronix e.K.                           | Dipl.-Ing. Robert Schwebel  |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2018-12-18 10:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 10:02 Oleksij Rempel
2018-12-15 10:02 ` [PATCH v1 2/3] MIPS: convert files with not precise GNU version " Oleksij Rempel
2018-12-17  6:33   ` Robert Schwebel
2018-12-15 10:02 ` [PATCH v1 3/3] MIPS: update to GPL-2.0-or-later for files copyrighted by me Oleksij Rempel
2018-12-18  7:32 ` [PATCH v1 1/3] MIPS: migrate all files to SPDX Antony Pavlov
2018-12-18  8:29   ` Oleksij Rempel
2018-12-18  9:32     ` Antony Pavlov
2018-12-18 10:52       ` Robert Schwebel [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=20181218105254.jsaewf5glubqh4wt@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=linux@rempel-privat.de \
    --cc=o.rempel@pengutronix.de \
    /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