From: Dan Williams <dan.j.williams@intel.com>
To: D Scott Phillips <d.scott.phillips@intel.com>
Cc: David Howells <dhowells@redhat.com>,
stuart hayes <stuart.w.hayes@gmail.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] uapi: Add the BSD-2-Clause license to ndctl.h
Date: Fri, 25 Oct 2019 15:45:33 -0700 [thread overview]
Message-ID: <CAPcyv4iQpO+JF8b7NUJUZ3fQFU=PWFeiWrXSd47QGnQPeRsrTg@mail.gmail.com> (raw)
In-Reply-To: <20191025175553.63271-1-d.scott.phillips@intel.com>
On Fri, Oct 25, 2019 at 10:55 AM D Scott Phillips
<d.scott.phillips@intel.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.
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next prev parent reply other threads:[~2019-10-25 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 17:55 [PATCH] uapi: Add the BSD-2-Clause license to ndctl.h D Scott Phillips
2019-10-25 21:52 ` Dexuan Cui
2019-10-25 22:45 ` Dan Williams [this message]
2019-10-25 22:56 ` Verma, Vishal L
2019-10-28 14:54 ` Kani, Toshi
2019-10-28 19:23 ` Jerry Hoemann
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='CAPcyv4iQpO+JF8b7NUJUZ3fQFU=PWFeiWrXSd47QGnQPeRsrTg@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=d.scott.phillips@intel.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=stuart.w.hayes@gmail.com \
/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).