From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPDX-License-Identifier: adding a comment section?
Date: Mon, 29 Jul 2013 08:57:08 -0400 [thread overview]
Message-ID: <51F666A4.9060406@ti.com> (raw)
In-Reply-To: <20130728154002.408853803E6@gemini.denx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/28/2013 11:40 AM, Wolfgang Denk wrote:
> Hello all,
>
> I need some help / recommendations how we should handle
> non-trivial license issues. For example, please have a look at the
> NE2000 network driver code:
>
> drivers/net/ne2000.h drivers/net/ne2000.c
> drivers/net/ne2000_base.h drivers/net/ne2000_base.c
>
> - First, these files include a statement that this code has been
> derived from Linux kernel and from eCOS sources and that it's
> released unter "GPL", but without stating wehter this means GPL-v2
> or GPL-v2+ or whatever.
>
> - Second, it includes the eCOS license header which basically says
> it's GPLv2+ plus some additional rights.
>
> - Third, if you track down the Linux source code mentioned above,
> this again says only "GPL" without additional specification.
>
>
> Two questions arise:
>
> - What should the resulting license(s) be in this specific case? I
> tend to interpret plain "GPL" as "GPLv2+", so we could probably
> summarize the license terms here as "eCos-2.0".
>
> What do you think?
I grabbed (because of the omap watchdog patch) 2.4.17, and that's (a)
older than our ne2k driver and (b) Already a GPLv2 and not 'or later'.
This is, I think, GPL-2.0.
> - I feel it would be helpful for future investigations if we are
> able to document our current understanding, so we don't have to
> re-investigate all this again and again each time we run into
> these files. My proposal is to define an additional "magic
> string"
>
> SPDX-License-Comments:
>
> which could be used to mark a text section that would contain such
> explanations.
>
> Wound this make sense, or do you have a better suggestion?
Sounds good. In this case we would say something like "Linux Kernel
driver and eCos driver files both used as reference".
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJR9majAAoJENk4IS6UOR1WCFEQAIDnb0TRvv1SL30MQVWkfRG7
oas1HQPBpLX0MUAt5M7NBHSh9KLgl/GA5aHX7CsgAUh0i7x2oO00x0wUdH59HEbV
UyJN0QbbYXmlceTXJzIEYP+GALzLtyg3GYE8JBwYOV3r5KV0askqlDoxq6A0354J
BjgfEc+GYyBiik1fHvAm64yAHOTd/m02WLYmHA+eNpNvYqrjlOmXI5/Kll6PJ28b
YAT4Jn7PY1rwxrFEVbDSWqq0ZsorkJDgpVjB4iwetGSJjS/Ov39kfDT3x8W7qXI8
5R9DzzIvhy80YXY54EUCFt2RvClJJd5uOa4SxTz9SfpI76KpSSzj8qq0hkFyXyOg
eRwcsTZUTnfSeNDu9IKV2SrxSDFdMWb58pej0fjkoxKvi2ID+8wuA0GJ/sS04IRo
reA7PlRPElc/e0YtsH87487qwNoRf8Bu11T98+QAbLLew6LBdSYKJlif114z+agY
1qzsb9KuC4gkSJYDLdY4pAxmu89GQXrpwAzIT5/mhv0fCmGxXo3HB5TmSxPpMHB+
MlzaBreZozaER7e9WhLpJ52XQK3w4t4C3VPMvz5onVekSs9NEBgf1OgRsYAdep96
dWJKGFpCle75MAs03jE0T8i7AquMpSx94MnsVJ2tJIxEQ6HRMFxg/Ux7IONvzRCa
fxRXJ0SYcg3JdFqRYvO0
=oO+C
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-07-29 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 15:40 [U-Boot] SPDX-License-Identifier: adding a comment section? Wolfgang Denk
2013-07-28 18:19 ` Roger Meier
2013-07-29 12:57 ` Tom Rini [this message]
2013-07-29 19:51 ` Wolfgang Denk
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=51F666A4.9060406@ti.com \
--to=trini@ti.com \
--cc=u-boot@lists.denx.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