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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADDK0KcnZBczz8fx2PN1aYUgSmXeBrX8Zn47Hn3O=fbbRuasRg@mail.gmail.com>
Date:	Tue, 18 Jun 2013 10:36:18 +0200
From:	Juan David Gonzalez Cobas <juan.david.gonzalez.cobas@...n.ch>
To:	Alessandro Rubini <rubini@...dd.com>
Cc:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	juan.david.gonzalez.cobas@...n.ch, cota@...ap.org,
	siglesias@...lia.com, rob@...dley.net, linux-doc@...r.kernel.org
Subject: Re: [PATCH 3/8] FMC: add core bus driver

On Tue, Jun 18, 2013 at 1:38 AM, Alessandro Rubini <rubini@...dd.com> wrote:
>>> + * Released according to the GNU GPL, version 2 or any later version.
[...]
> I think we want to allow for proprietary FMC drivers. I personally
> don't feel this is a core kernel technology.  But I'll let David Cobas
> expand on CERN policies, as I'm only a consultant.

After some discussion, we think Alessandro's arguments about keeping
EXPORT_SYMBOL are sound. As mentioned, CERN policies are
non-restrictive in this sense, hence we consider correct to leave
EXPORT_SYMBOLs as they are currently. The BSD licencing for
the other, "public domain" examples is also OK.

Hope this helps,

        david
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ