From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] i2c-tools: include LGPL-2.1+ license for libi2c
Date: Fri, 24 Aug 2018 23:57:59 +0200 [thread overview]
Message-ID: <20180824235759.4edac1f1@windsurf> (raw)
In-Reply-To: <1535118847-21086-2-git-send-email-brad@nextdimension.cc>
Hello,
On Fri, 24 Aug 2018 08:54:06 -0500, Brad Love wrote:
> Extend i2c-tools SPDX identifiers to include the library license.
> Also include COPYING.LGPL and README to license files.
>
> The ic2-tools readme states:
>
> LICENSE
>
> Check the documentation of individual tools for licensing information.
> The library is released under the LGPL version 2.1 or later, while most
> tools are released under the GPL version 2 or later, but there are a few
> exceptions.
>
> Signed-off-by: Brad Love <brad@nextdimension.cc>
I've applied to master, but after adding the hashes of the additional
license files to i2c-tools.hash.
Yann: is it expected than missing hashes for license files is not a
hard failure, when a hash file is present ? Perhaps it was back in the
days, but maybe we should tighten up this ?
Or at least in the case where one of the license files has a hash that
is present, which was the case here.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-24 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 13:54 [Buildroot] [PATCH v3 0/2] i2c-tools: license and staging installation fixes Brad Love
2018-08-24 13:54 ` [Buildroot] [PATCH v3 1/2] i2c-tools: include LGPL-2.1+ license for libi2c Brad Love
2018-08-24 21:57 ` Thomas Petazzoni [this message]
2018-08-24 22:06 ` Yann E. MORIN
2018-08-24 13:54 ` [Buildroot] [PATCH v3 2/2] i2c-tools: install library and header to staging Brad Love
2018-08-24 22:04 ` Thomas Petazzoni
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=20180824235759.4edac1f1@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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