linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: linux-i2c@vger.kernel.org
Subject: Re: i2c-tools: library licensing issues
Date: Wed, 29 Nov 2017 07:35:24 +0100	[thread overview]
Message-ID: <20171129073524.5596967f@endymion> (raw)
In-Reply-To: <20171125164717.kg5vv6zsuztr3vkn@aurel32.net>

Hi Aurélien,

On Sat, 25 Nov 2017 17:47:17 +0100, Aurelien Jarno wrote:
> I have been reviewing the i2c-tools licensing, and it seems there is a
> contradiction between README and lib/smbus.c about the library
> licensing:
> 
> From README:
> | 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.
> 
> From lib/smbus.c:
> | This program is free software; you can redistribute it and/or modify
> | it under the terms of the GNU General Public License as published by
> | the Free Software Foundation; either version 2 of the License, or
> | (at your option) any later version.
> 
> On the other hand, the license in lib/Module.mk matches the one from
> README.
> 
> I guess one of README or lib/smbus.c has to be fixed. Can someone
> clarify that? In meantime I think the library as a whole should be
> considered as GPL v2 or later.

Thanks for pointing out this inconsistency, which I missed. 


-- 
Jean Delvare
SUSE L3 Support

      reply	other threads:[~2017-11-29  6:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25 16:47 i2c-tools: library licensing issues Aurelien Jarno
2017-11-29  6:35 ` Jean Delvare [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=20171129073524.5596967f@endymion \
    --to=jdelvare@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=linux-i2c@vger.kernel.org \
    /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).