LKML Archive on
help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <>
To: "Rafał Miłecki" <>,
	"One Thousand Gnomes" <>
Cc: Greg Kroah-Hartman <>,
	Thomas Gleixner <>,
	LKML <>,
	Jonathan Corbet <>,
	Linus Torvalds <>,
	Andrew Morton <>,
	Kate Stewart <>,
	Philippe Ombredanne <>,
	Christoph Hellwig <>,
	Russell King <>,
	Rob Herring <>,
	Jonas Oberg <>, Joe Perches <>,,
	Kate Stewart <>,
	Florian Fainelli <>,
Subject: Re: LICENSES: Missing ISC text & possibly a category ("Not recommended" vs. "Preferred licenses")
Date: Sun, 29 Apr 2018 07:31:01 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, Apr 29, 2018 at 07:03:15AM +0000, Luis R. Rodriguez wrote:
> On Sun, Apr 29, 2018 at 07:26:17AM +0200, Greg Kroah-Hartman wrote:
> > I see it is only used in a very small number of dts files.  Why not just
> > use BSD-2-Clause instead?  What do you find in ISC that is not available
> > to you with just BSD?
> ISC license is a simplified version of the BSD license due to the Berne
> convention. It was also used for wireless drivers to help the BSD community in
> particular OpenBSD who had picked that license for new contributions claimed
> simplification of the BSD-2-Clause. Because of this reason many BSD communities
> feel super comfortable with picking up kernel code in Linux under this license.
> Granted, I'm on no longer a fan of promoting permissive licenses as it didn't
> buy us cross-collaboration at all. We tried.
> But it would be unfair to advice against a license unless a reason is stated in
> favor of another BSD license. Why is the ISC license worse than the
> BSD-2-Clause?

Here's a good 'ol discussed reason as to why to prefer the 2-clause BSD
I suppose, and also to consider dual licensing actually:

So essentially tested over time, runtime considerations, and whatever the FSF
decides today may change tomorrow. So best to be safe. The dual licensing
strategy also helps with "unanticipated incompatibility".


  reply	other threads:[~2018-04-29  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-28 21:25 Rafał Miłecki
2018-04-29  5:26 ` Greg Kroah-Hartman
2018-04-29  7:03   ` Luis R. Rodriguez
2018-04-29  7:31     ` Luis R. Rodriguez [this message]
2018-04-29 10:15   ` Rafał Miłecki
2018-04-30  0:09     ` Greg Kroah-Hartman

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: LICENSES: Missing ISC text & possibly a category ("Not recommended" vs. "Preferred licenses")' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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