linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Huntsman <bryanh@codeaurora.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>, Gregory Bean <gbean@codeaurora.org>,
	dwalker@codeaurora.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] msm: Add gpio register address mapping information.
Date: Mon, 21 Jun 2010 10:28:33 -0700	[thread overview]
Message-ID: <4C1FA141.30006@codeaurora.org> (raw)
In-Reply-To: <20100621181851.53de5f62@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>>> Yeah. Either this can be replaced with GPL, and it such case just do
>>> so, or it can not, and then it can not be applied to kernel.
>>>
>> This is a standard BSD-style license so it's compatible w/ the GPL.  Thanks.
> 
> The kernel requires GPL, and its much much easier for everyone to state
> so explicitly to avoid future surprises (remember 4 clause BSD was once
> thought GPL compatible even by the FSF...)
> 
> If you want to make it clear it's also available BSD licensed in this
> form (at least until someone changes it) see the wording in files like
> drivers/char/random.c
> 
> That usually keeps all the lawyers happy.
> 
> Alan

Keeping the lawyers happy certainly has it's challenges.  Is it uncommon 
to use just a BSD-style license for headers?  I understand that everyone 
would prefer just GPL.  I'm primarily curious about preserving BSD 
licensing for headers under /include.  A dual license would work, but 
would it also be frowned upon to use just a 3-clause BSD license like we 
have in this patch?  Thanks.

- Bryan

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2010-06-21 17:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 19:12 [PATCH 0/3] msm: Add gpiolib devices to MSM7x30 and QSD8x50 Gregory Bean
2010-06-18 19:12 ` [PATCH 1/3] msm: Add gpio register address mapping information Gregory Bean
2010-06-19 20:02   ` Pavel Machek
2010-06-21 17:03     ` Bryan Huntsman
2010-06-21 17:18       ` Alan Cox
2010-06-21 17:28         ` Bryan Huntsman [this message]
2010-06-21 19:08           ` Alan Cox
2010-06-21 17:51         ` Daniel Walker
2010-06-21 17:27       ` Pavel Machek
2010-06-18 19:12 ` [PATCH 2/3] msm: 7x30: Add gpio device configuration Gregory Bean
2010-06-18 19:12 ` [PATCH 3/3] msm: 8x50: add " Gregory Bean
2010-06-18 21:59   ` Daniel Walker
2010-06-18 19:26 ` [PATCH 0/3] msm: Add gpiolib devices to MSM7x30 and QSD8x50 Daniel Walker

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=4C1FA141.30006@codeaurora.org \
    --to=bryanh@codeaurora.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dwalker@codeaurora.org \
    --cc=gbean@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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).