linux-kernel - Re: [PATCH] uapi: Add the BSD-2-Clause license to ndctl.h

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]

Date:   Fri, 25 Oct 2019 22:56:40 +0000
From:   "Verma, Vishal L" <vishal.l.verma@...el.com>
To:     "Williams, Dan J" <dan.j.williams@...el.com>,
        "Phillips, D Scott" <d.scott.phillips@...el.com>
CC:     "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
        "decui@...rosoft.com" <decui@...rosoft.com>,
        "jerry.hoemann@....com" <jerry.hoemann@....com>,
        "toshi.kani@....com" <toshi.kani@....com>,
        "stuart.w.hayes@...il.com" <stuart.w.hayes@...il.com>,
        "dhowells@...hat.com" <dhowells@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] uapi: Add the BSD-2-Clause license to ndctl.h


On Fri, 2019-10-25 at 15:45 -0700, Dan Williams wrote:
> On Fri, Oct 25, 2019 at 10:55 AM D Scott Phillips
> <d.scott.phillips@...el.com> wrote:
> > Allow ndctl.h to be licensed with BSD-2-Clause so that other
> > operating systems can provide the same user level interface.
> > ---
> > 
> > I've been working on nvdimm support in FreeBSD and would like to
> > offer the same ndctl API there to ease porting of application
> > code. Here I'm proposing to add the BSD-2-Clause license to this
> > header file, so that it can later be copied into FreeBSD.
> > 
> > I believe that all the authors of changes to this file (in the To:
> > list) would need to agree to this change before it could be
> > accepted, so any signed-off-by is intentionally ommited for now.
> > Thanks,
> 
> I have no problem with this change, but let's take the opportunity to
> let SPDX do its job and drop the full license text.

This is fine by me too, barring the full license text vs. SPDX caveat
Dan mentions.