mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] arch/arm/boards: Replace license and copyright boilerplate by SPDX identfiers
Date: Sat, 23 May 2020 17:06:40 +0200	[thread overview]
Message-ID: <20200523150640.jvuctfcne2lwuomw@pengutronix.de> (raw)
In-Reply-To: <20200523150007.erjwm3azjdyaywx4@pengutronix.de>

On Sat, May 23, 2020 at 05:00:07PM +0200, Roland Hieber wrote:
> On Tue, Apr 28, 2020 at 03:24:05PM +0200, Uwe Kleine-König wrote:
> > This adapts all files that were identifed by licensecheck
> > (https://salsa.debian.org/build-common-team/licensecheck.git) as
> > licensed under the GPL.
> > 
> > The advantage is that these specifiers are machine-parseable which helps
> > license conformance, e.g. for packaging barebox in Debian.
> > 
> > While touching these files also do some minor comment reformatting to
> > get some uniform layout.
> > 
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> 
> Hmmm, I don't see why you dropped the following files from your
> (implicit) v2:
> 
> arch/arm/boards/embedsky-e9/board.c
> arch/arm/boards/eukrea_cpuimx27/eukrea_cpuimx27.c
> arch/arm/boards/eukrea_cpuimx35/eukrea_cpuimx35.c
> arch/arm/boards/freescale-mx21-ads/imx21ads.c
> arch/arm/boards/freescale-mx35-3ds/3stack.c
> arch/arm/boards/freescale-mx6-sabresd/board.c
> arch/arm/boards/friendlyarm-mini2440/mini2440.c
> arch/arm/boards/friendlyarm-tiny210/tiny210.c
> arch/arm/boards/globalscale-guruplug/board.c 
> arch/arm/boards/globalscale-mirabox/board.c
> arch/arm/boards/imx233-olinuxino/imx23-olinuxino.c
> arch/arm/boards/karo-tx6x/board.c
> arch/arm/boards/phytec-phycard-omap3/pca-a-l1.c
> arch/arm/boards/phytec-phycore-pxa270/config.h
> arch/arm/boards/variscite-mx6/board.c
> arch/arm/boards/variscite-mx6/lowlevel.c
> arch/arm/boards/versatile/versatilepb.c
> arch/arm/boards/zylonite/zylonite.h
> 
> Other than that, what's there is correct, so
> Reviewed-by: Roland Hieber <rhi@pengutronix.de>

Uhm, this was meant for v2, but I replied to the wrong thread, but your
v2 also didn't have "v2" in the subject, so I got confused :P

 - Roland

-- 
Roland Hieber, Pengutronix e.K.          | r.hieber@pengutronix.de     |
Steuerwalder Str. 21                     | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686         | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-05-23 15:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 13:24 Uwe Kleine-König
2020-04-29 10:50 ` Roland Hieber
2020-04-29 13:41   ` Uwe Kleine-König
2020-04-29 15:52     ` Roland Hieber
2020-05-23 15:00 ` Roland Hieber
2020-05-23 15:06   ` Roland Hieber [this message]
2020-05-25 20:42   ` Uwe Kleine-König
2020-05-19 16:37 Uwe Kleine-König
2020-05-19 19:49 ` Uwe Kleine-König
2020-07-01 19:56   ` Uwe Kleine-König
2020-05-25  5:54 ` Sascha Hauer
2020-05-25 20:34   ` Roland Hieber

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=20200523150640.jvuctfcne2lwuomw@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=u.kleine-koenig@pengutronix.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