linux-kernel - Re: [PATCH 1/3] msm: Add gpio register address mapping information.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100621200852.6f80b631@lxorguk.ukuu.org.uk>
Date:	Mon, 21 Jun 2010 20:08:52 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Bryan Huntsman <bryanh@...eaurora.org>
Cc:	Pavel Machek <pavel@....cz>, Gregory Bean <gbean@...eaurora.org>,
	dwalker@...eaurora.org, linux-arm-msm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] msm: Add gpio register address mapping information.

> 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.

The problem if it is only 3 clause BSD is what happens if somehow
somewhere 3 clause BSD and GPL turn out to be incompatible. The easiest
way to avoid that is to explicitly put it under both.

It's not likely to happen but its also easy to protect against
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/