(trying this again, as first time, my message bounced) I just saw this and have not followed the entire thread from the beginning, but if you are unsure if a given license text to something on the SPDX License List, I highly recommend using the SPDX License-diff browser extension / add-on (for Chrome or Firefox) - once you have that, you can simply highlight a text in your browser window and it will tell you if it matches or how far off it is if not.
If a license is NOT a match to anything on the SPDX License List, please submit it to the SPDX legal team here: https://tools.spdx.org/app/submit_new_license/ (and preferably then tag me in the Github issue, my Github ide is @jlovejoy ) Please make sure to include that it's in the LInux kernel and a link to where you found it. More about requesting a new license be added to the SPDX License List can be found here: https://github.com/spdx/license-list-XML/blob/master/DOCS/request-new-license.md Thanks! Jilayne SPDX legal team co-lead > On Jan 21, 2022, at 10:17 AM, Richard Fontana <rfont...@redhat.com> wrote: > > On Fri, Jan 21, 2022 at 6:03 AM Christophe Leroy > <christophe.le...@csgroup.eu> wrote: >> >> Several files are missing SPDX license identifiers. >> >> Following files are given the following SPDX identifier based on the >> comments in the top of the file: >> >> include/asm/ibmebus.h:/* SPDX-License-Identifier: GPL-2.0 OR OpenIB >> BSD */ > [...] >> platforms/pseries/ibmebus.c:// SPDX-License-Identifier: GPL-2.0 OR >> OpenIB BSD > > "OpenIB BSD" is not a defined SPDX identifier. There is an SPDX > identifier "Linux-OpenIB" > https://spdx.org/licenses/Linux-OpenIB.html > but I believe that is not a match to what's in these files > (specifically, the wording of the disclaimer), rather I believe what > you want here is BSD-2-Clause, but you may want to check that. > > Richard >
