linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	Rob Herring <robh+dt@kernel.org>,
	linux-spdx@vger.kernel.org,
	Devicetree Compiler <devicetree-compiler@vger.kernel.org>,
	DTML <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frank Rowand <frowand.list@gmail.com>
Subject: Re: SPDX conversion under scripts/dtc/ of Linux Kernel
Date: Wed, 19 Jun 2019 14:59:48 +0200	[thread overview]
Message-ID: <20190619125948.GA27090@kroah.com> (raw)
In-Reply-To: <CAK7LNARHHXv5Tu4BHN1avKOExS6HmPfd2c0ELZiQaxtmETOsDw@mail.gmail.com>

On Wed, Jun 19, 2019 at 07:23:19PM +0900, Masahiro Yamada wrote:
> Hi.
> 
> In this development cycle of Linux kernel,
> lots of files were converted to use SPDX
> instead of the license boilerplate.
> 
> However.
> 
> Some files were imported from a different project,
> and are periodically synchronized with the upstream.
> Have we discussed what to do about this case?
> 
> 
> For example, scripts/dtc/ is the case.
> 
> The files in scripts/dtc/ are synced with the upstream
> device tree compiler.
> 
> Rob Herring periodically runs scripts/dtc/update-dtc-source.sh
> to import outcome from the upstream.
> 
> 
> The upstream DTC has not adopted SPDX yet.
> 
> Some files in Linux (e.g. scripts/dtc/dtc.c)
> have been converted to SPDX.
> 
> So, they are out of sync now.
> 
> The license boilerplate will come back
> when Rob runs scripts/dtc/update-dtc-source.sh
> next time.
> 
> What shall we do?
> 
> [1] Convert upstream DTC to SPDX
> 
> This will be a happy solution if it is acceptable in DTC.
> Since we cannot push the decision of the kernel to a different
> project, this is totally up to David Gibson.

That's fine with me :)

> [2] Change scripts/dtc/update-dtc-source.sh to
>     take care of the license block somehow

That would also be good.

> [3] Go back to license boilerplate, and keep the files
>     synced with the upstream
>     (and scripts/dtc/ should be excluded from the
>      SPDX conversion tool.)

nothing is being excluded from the SPDX conversions, sorry.  The goal is
to do this for every file in the kernel tree.  Otherwise it's pointless.

> Or, what else?

Rob remembers to keep those first lines of the files intact when doing
the next sync?

thanks,

greg k-h

  reply	other threads:[~2019-06-19 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 10:23 SPDX conversion under scripts/dtc/ of Linux Kernel Masahiro Yamada
2019-06-19 12:59 ` Greg Kroah-Hartman [this message]
2019-06-19 15:39   ` Rob Herring
2019-06-20  7:45     ` David Gibson

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=20190619125948.GA27090@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).