Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 6/7] liburcu: Add nios2 support
Date: Wed, 10 Feb 2016 12:58:04 +0100	[thread overview]
Message-ID: <201602101258.04846.marex@denx.de> (raw)
In-Reply-To: <2564154.XB0jvojI47@peggleto-mobl.ger.corp.intel.com>

On Wednesday, February 10, 2016 at 10:05:52 AM, Paul Eggleton wrote:
> On Tue, 09 Feb 2016 18:56:09 Marek Vasut wrote:
> > On Tuesday, February 09, 2016 at 06:52:12 PM, Khem Raj wrote:
> > > > On Feb 9, 2016, at 4:07 AM, Marek Vasut <marex@denx.de> wrote:
> > > > 
> > > > On Tuesday, February 09, 2016 at 12:53:01 PM, Burton, Ross wrote:
> > > >> On 9 February 2016 at 11:31, Marek Vasut <marex@denx.de> wrote:
> > > >>> -LIC_FILES_CHKSUM =
> > > >>> "file://LICENSE;md5=0f060c30a27922ce9c0d557a639b4fa3 \
> > > >>> +LIC_FILES_CHKSUM =
> > > >>> "file://LICENSE;md5=e548d28737289d75a8f1e01ba2fd7825 \
> > > >> 
> > > >> Why did the license checksum change?
> > > > 
> > > > Because the LICENSE file now contains one more entry for nios2, which
> > > > changed the checksum of the whole file. Maybe we should trim the
> > > > checksum to use only the header in the LICENSE file and not the whole
> > > > file to prevent this ?
> > > > 
> > > > This is the change which triggered the change of the checksum:
> > > > 
> > > > +diff --git a/LICENSE b/LICENSE
> > > > +index 3147094..a06fdcc 100644
> > > > +--- a/LICENSE
> > > > ++++ b/LICENSE
> > > > +@@ -45,6 +45,7 @@ compiler.h
> > > > + arch/s390.h
> > > > + uatomic/alpha.h
> > > > + uatomic/mips.h
> > > > ++uatomic/nios2.h
> > > 
> > > I don’t know how the LICENSE file looks like but including file names
> > > in license file is probably worth ignoring in checksums.
> > 
> > See below:
> > 
> > Userspace RCU library licensing
> > Mathieu Desnoyers
> > September 3, 2012
> > 
> > 
> > * LGPLv2.1
> > 
> > The library part is distributed under LGPLv2.1 or later. See lgpl-2.1.txt
> > for license details. Refer to the individual file headers for details.
> > 
> > LGPL-compatible source code can statically use the library header using :
> > 
> > #define _LGPL_SOURCE
> > #include <urcu.h>
> > 
> > Dynamic-only linking with the LGPL library is used if _LGPL_SOURCE is not
> > defined. It permits relinking with newer versions of the library, which
> > is required by the LGPL license.
> > 
> > See lgpl-relicensing.txt for details.
> > 
> > 
> > * MIT-style license :
> > 
> > xchg() primitive has been rewritten from scratch starting from atomic_ops
> > 1.2 which has a MIT-style license that is intended to allow use in both
> > 
> > free and proprietary software:
> >         http://www.hpl.hp.com/research/linux/atomic_ops/LICENSING.txt
> >         http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/
> > 
> > This MIT-style license (BSD like) apply to:
> > 
> > uatomic/gcc.h
> > uatomic/unknown.h
> > uatomic/generic.h
> > uatomic/sparc64.h
> > uatomic/arm.h
> > uatomic/ppc.h
> > uatomic/x86.h
> > uatomic.h
> > 
> > MIT/X11 (BSD like) license apply to:
> > 
> > compiler.h
> > arch/s390.h
> > uatomic/alpha.h
> > uatomic/mips.h
> > uatomic/nios2.h
> > uatomic/s390.h
> > system.h
> > 
> > 
> > * GPLv2
> > 
> > Library test code is distributed under the GPLv2 license. See gpl-2.0.txt
> > for license details. See headers of individual files under tests/ for
> > details.
> > 
> > 
> > * GPLv3 (or later)
> > 
> > The following build-related macro is under GPLv3 (or later):
> > 
> > m4/ax_tls.m4
> 
> If you only point to part of this file you are risking missing the addition
> of just about any license to the end of the list on a future upgrade. That
> doesn't sound like a good idea to me.

Hm, ouch. In that case, I guess we should stick with the current situation and
update the license file checksum if needed ?


  reply	other threads:[~2016-02-10 11:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 11:31 [PATCH 1/7] strace: Fix build for arc, metag, nios2, or1k, tile Marek Vasut
2016-02-09 11:31 ` [PATCH 2/7] binutils: Repair nios2 PLT and GP handling Marek Vasut
2016-02-09 11:57   ` Burton, Ross
2016-02-09 13:08   ` [PATCH V2 " Marek Vasut
2016-02-09 14:21     ` Burton, Ross
2016-02-09 14:29       ` Marek Vasut
2016-02-09 16:00         ` Randy MacLeod
2016-02-09 16:52           ` Marek Vasut
2016-02-09 11:31 ` [PATCH 3/7] dpkg: Update to 1.18.4 Marek Vasut
2016-02-09 11:31 ` [PATCH 4/7] guile: Fix nios2 support Marek Vasut
2016-02-09 11:31 ` [PATCH 5/7] nspr: Add " Marek Vasut
2016-02-09 11:31 ` [PATCH 6/7] liburcu: " Marek Vasut
2016-02-09 11:53   ` Burton, Ross
2016-02-09 12:07     ` Marek Vasut
2016-02-09 13:24       ` Burton, Ross
2016-02-09 17:52       ` Khem Raj
2016-02-09 17:56         ` Marek Vasut
2016-02-10  9:05           ` Paul Eggleton
2016-02-10 11:58             ` Marek Vasut [this message]
2016-02-09 11:31 ` [PATCH 7/7] oprofile: " Marek Vasut
2016-02-09 11:51 ` [PATCH 1/7] strace: Fix build for arc, metag, nios2, or1k, tile Burton, Ross
2016-02-09 13:06   ` Marek Vasut
2016-02-09 13:07 ` [PATCH V2 " Marek Vasut

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=201602101258.04846.marex@denx.de \
    --to=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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