From: Doug Ledford <dledford@redhat.com>
To: David Miller <davem@davemloft.net>, jgg@mellanox.com
Cc: linux-rdma@vger.kernel.org, kstewart@linuxfoundation.org,
pombredanne@nexb.com, gregkh@linuxfoundation.org,
tglx@linutronix.de, swinslow@linuxfoundation.org,
santosh.shilimkar@oracle.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, davejwatson@fb.com
Subject: Re: [PATCH for-rc] uapi: Fix SPDX tags for files referring to the 'OpenIB.org' license
Date: Mon, 23 Apr 2018 11:11:06 -0400 [thread overview]
Message-ID: <1524496266.11756.36.camel@redhat.com> (raw)
In-Reply-To: <20180422.210823.1454088204642743739.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On Sun, 2018-04-22 at 21:08 -0400, David Miller wrote:
> From: Jason Gunthorpe <jgg@mellanox.com>
> Date: Fri, 20 Apr 2018 09:49:10 -0600
>
> > Based on discussion with Kate Stewart this license is not a
> > BSD-2-Clause, but is now formally identified as Linux-OpenIB
> > by SPDX.
> >
> > The key difference between the licenses is in the 'warranty'
> > paragraph.
> >
> > if_infiniband.h refers to the 'OpenIB.org' license, but
> > does not include the text, instead it links to an obsolete
> > web site that contains a license that matches the BSD-2-Clause
> > SPX. There is no 'three clause' version of the OpenIB.org
> > license.
> >
> > Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
>
> Acked-by: David S. Miller <davem@davemloft.net>
>
Thanks, applied.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-04-23 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 15:49 [PATCH for-rc] uapi: Fix SPDX tags for files referring to the 'OpenIB.org' license Jason Gunthorpe
2018-04-23 1:08 ` David Miller
2018-04-23 15:11 ` Doug Ledford [this message]
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=1524496266.11756.36.camel@redhat.com \
--to=dledford@redhat.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@mellanox.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=santosh.shilimkar@oracle.com \
--cc=swinslow@linuxfoundation.org \
--cc=tglx@linutronix.de \
/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).