All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: netdev@vger.kernel.org
Cc: Jon Smirl <jonsmirl@gmail.com>,
	"Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	Christoph Hellwig <hch@infradead.org>,
	Jiri Slaby <jirislaby@gmail.com>,
	linville@tuxdriver.com, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 4/5] Net: ath5k, license is GPLv2
Date: Thu, 30 Aug 2007 10:26:53 +0200	[thread overview]
Message-ID: <20070830082652.GA2669@ff.dom.local> (raw)
In-Reply-To: <200708292137.48834.mb@bu3sch.de>

On 29-08-2007 21:37, Michael Buesch wrote:
> On Wednesday 29 August 2007 21:33:43 Jon Smirl wrote:
>> What if a patch spans both code that is pure GPL and code imported
>> from BSD, how do you license it?
> 
> I think it's a valid assumption, if we say that the author
> of the patch read the license header of a file and agreed with it.
> So the patch is licensed to whatever the fileheader says. And if
> there's none, it's licensed with the COPYING terms.
> If a patch author likes some other license conditions, he must
> explicitely add them with the patch to the file, saying that this
> and that part have these and those conditions. Of course they must
> be compatible with the original license.
> 

I didn't track this thread from the beginning, so maybe I repeat
somebody's ideas (probably like above), but IMHO: do we have to be
so selfish/pedantic? Can't we sometimes 'donate' a little bit to our
'older' bsd cousins or half-brothers? I think, it could be like this:

- if our changes are minor and authors of these changes don't mind
the file could stay BSD licensed only; plus we ask BSD to let it be
dual licensed (but no big hassle);

- otherwise, we should always distinctly mark all GPL parts.

Regards,
Jarek P.

PS: there is probably some mess with gmail addresses in this thread.

WARNING: multiple messages have this Message-ID (diff)
From: Jarek Poplawski <jarkao2@o2.pl>
To: netdev@vger.kernel.org
Cc: Jon Smirl <jonsmirl@gmail.com>,
	"Valdis\.Kletnieks\@vt\.edu" <Valdis.Kletnieks@vt.edu>,
	Christoph Hellwig <hch@infradead.org>,
	Jiri Slaby <jirislaby@gmail.com>,
	linville@tuxdriver.com, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 4/5] Net: ath5k, license is GPLv2
Date: Thu, 30 Aug 2007 10:26:53 +0200	[thread overview]
Message-ID: <20070830082652.GA2669@ff.dom.local> (raw)
In-Reply-To: <200708292137.48834.mb@bu3sch.de>

On 29-08-2007 21:37, Michael Buesch wrote:
> On Wednesday 29 August 2007 21:33:43 Jon Smirl wrote:
>> What if a patch spans both code that is pure GPL and code imported
>> from BSD, how do you license it?
> 
> I think it's a valid assumption, if we say that the author
> of the patch read the license header of a file and agreed with it.
> So the patch is licensed to whatever the fileheader says. And if
> there's none, it's licensed with the COPYING terms.
> If a patch author likes some other license conditions, he must
> explicitely add them with the patch to the file, saying that this
> and that part have these and those conditions. Of course they must
> be compatible with the original license.
> 

I didn't track this thread from the beginning, so maybe I repeat
somebody's ideas (probably like above), but IMHO: do we have to be
so selfish/pedantic? Can't we sometimes 'donate' a little bit to our
'older' bsd cousins or half-brothers? I think, it could be like this:

- if our changes are minor and authors of these changes don't mind
the file could stay BSD licensed only; plus we ask BSD to let it be
dual licensed (but no big hassle);

- otherwise, we should always distinctly mark all GPL parts.

Regards,
Jarek P.

PS: there is probably some mess with gmail addresses in this thread.

  reply	other threads:[~2007-08-30  8:27 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28 15:58 [PATCH 1/5] Net: ath5k, split hw into hw, phy and initvals Jiri Slaby
2007-08-28 15:59 ` [PATCH 2/5] Net: ath5k, switch to ioread/iowrite Jiri Slaby
2007-08-28 16:00 ` [PATCH 3/5] Net: ath5k, use int as retval Jiri Slaby
2007-08-30 12:40   ` John W. Linville
2007-08-30 12:40     ` John W. Linville
2007-09-01 20:08     ` Jiri Slaby
2007-09-01 20:08       ` Jiri Slaby
2007-09-02 15:55       ` Nick Kossifidis
2007-09-02 15:55         ` Nick Kossifidis
2007-09-03  6:34         ` Jiri Slaby
2007-09-03 13:37           ` Nick Kossifidis
2007-08-28 16:00 ` [PATCH 4/5] Net: ath5k, license is GPLv2 Jiri Slaby
2007-08-28 17:11   ` Christoph Hellwig
2007-08-28 20:11     ` Luis R. Rodriguez
2007-08-29 17:29     ` Valdis.Kletnieks
2007-08-29 18:01       ` Jon Smirl
2007-08-29 18:28         ` Alan Cox
2007-08-29 19:33           ` Jon Smirl
2007-08-29 19:33             ` Jon Smirl
2007-08-29 19:37             ` Michael Buesch
2007-08-29 19:37               ` Michael Buesch
2007-08-30  8:26               ` Jarek Poplawski [this message]
2007-08-30  8:26                 ` Jarek Poplawski
2007-08-30  8:32                 ` Jarek Poplawski
2007-08-30  8:32                   ` Jarek Poplawski
2007-08-29 19:45             ` Alan Cox
2007-08-30 13:45               ` Jarek Poplawski
2007-08-30 13:02             ` David Newall
2007-08-29  9:59   ` Johannes Berg
2007-08-29  9:59     ` Johannes Berg
2007-08-29 10:35     ` Jiri Slaby
2007-08-29 10:35       ` Jiri Slaby
2007-08-29 13:13       ` Xavier Bestel
2007-08-30 11:59         ` Johannes Berg
2007-08-30 11:59           ` Johannes Berg
2007-08-28 16:01 ` [PATCH 5/5] Net: ath5k, kconfig changes Jiri Slaby
2007-08-28 17:13   ` Christoph Hellwig
2007-08-30  1:38     ` Nick Kossifidis
2007-08-30 12:35       ` Christoph Hellwig
2007-08-30 12:35         ` Christoph Hellwig
2007-08-30 12:36       ` John W. Linville
2007-08-30 12:36         ` John W. Linville
2007-08-30 22:18         ` Nick Kossifidis
2007-09-01  5:58           ` Nick Kossifidis
2007-09-01  5:58             ` Nick Kossifidis
2007-08-31 11:58         ` Dan Williams
2007-08-31 11:58           ` Dan Williams
2007-08-31 13:30           ` Jeff Garzik
2007-08-31 13:30             ` Jeff Garzik
2007-08-31 14:32             ` Dan Williams
2007-08-28 16:22 ` [PATCH 1/5] Net: ath5k, split hw into hw, phy and initvals Johannes Berg
2007-08-28 17:08 ` Christoph Hellwig
2007-08-28 17:10 ` Christoph Hellwig
2007-08-28 17:33   ` Johannes Berg
2007-08-28 17:47     ` Larry Finger
2007-08-28 21:50       ` Luis R. Rodriguez
2007-08-30  1:50   ` Nick Kossifidis
2007-08-30  1:50     ` Nick Kossifidis
2007-08-30 12:38     ` John W. Linville
2007-08-30 12:38       ` John W. Linville
2007-09-01  3:12       ` Nick Kossifidis
2007-09-01  3:12         ` Nick Kossifidis

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=20070830082652.GA2669@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hch@infradead.org \
    --cc=jirislaby@gmail.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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 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.