On Wed, 2018-03-07 at 13:54 -0700, Jason Gunthorpe wrote:
> On Wed, Mar 07, 2018 at 03:39:53PM -0500, Doug Ledford wrote:
> > On Wed, 2018-03-07 at 14:36 -0600, Steve Wise wrote:
> > > >
> > > > BTW, if you can get a v5 of just this patch using the license indicators
> > > > before Leon responds to my email, we can get things in the right way
> > > > from the beginning ;-)
> > > >
> > >
> > > So it would look something like this? The copyrights are from cma.c, which is the origin of the contents of this new header.
> > >
> > > /* SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause) */
> > > /* Copyright (c) 2005 Voltaire Inc. All rights reserved.
> > > * Copyright (c) 2002-2005, Network Appliance, Inc. All rights reserved.
> > > * Copyright (c) 1999-2005, Mellanox Technologies, Inc. All rights reserved.
> > > * Copyright (c) 2005-2006 Intel Corporation. All rights reserved.
> > > */
> > >
> > >
> >
> > Yep, pretty much. Although, I think the BSD in the file might have been
> > the BSD 2 clause. Jason is more familiar with the BSD variants than I
> > am. Jason?
>
> Hmm..
>
> Actually no, the OpenIB license we use does not match any existing
> SPDX identifier, so we can't take code covered under that license and
> apply SPDX at this time.
>
> The issue is that the standard license in the kernel is the start of
> the standard BSD 2 clause license followed by the end of the standard
> MIT license.
>
> From what I understand about the SPDX rules on their web site, this
> means it is no match to any existing license I can find (and I checked
> the raw text in their git repo)
>
> I supposed we should talk to the SPDX people and get the tags we need?
> Maybe I'll look at that..
>
> Jason
That being the case Steve, we obviously will have to fix this up later,
and the current patch is fine.
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDDAttachment:
signature.asc
Description: This is a digitally signed message part
