From: Neil Armstrong <narmstrong@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: khilman@baylibre.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 00/10] ARM: meson: update with SPDX Licence identifier
Date: Mon, 20 May 2019 20:34:31 +0200 [thread overview]
Message-ID: <5CE2F337.9060207@baylibre.com> (raw)
In-Reply-To: <CAFBinCCEi8OjeDaWxfhyfoQOu3GVsw=U9jBLQ2LEkPn7Ataf7w@mail.gmail.com>
Le 20/05/2019 20:06, Martin Blumenstingl a écrit :
> Hi Neil,
>
> On Mon, May 20, 2019 at 4:38 PM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>
>> Update the SPDX Licence identifier for the Amlogic DT and mach-meson
>> files.
>>
>> Neil Armstrong (10):
>> ARM: dts: meson: update with SPDX Licence identifier
>> ARM: dts: meson6-atv1200: update with SPDX Licence identifier
>> ARM: dts: meson6: update with SPDX Licence identifier
>> ARM: dts: meson8-minix-neo-x8: update with SPDX Licence identifier
>> ARM: dts: meson8: update with SPDX Licence identifier
>> ARM: dts: meson8b-mxq: update with SPDX Licence identifier
>> ARM: dts: meson8b-odroidc1: update with SPDX Licence identifier
>> ARM: dts: meson8b: update with SPDX Licence identifier
> please check the .dts updates with my comment on the meson8b patch
> because I believe there are two typos (which managed to sneak into the
> rest of the patches)
You are right, thanks for pointing me to the licenses texts subtleties, I was misled by
the "of the GPL or the X11 license"... but looking closely clearly shows
a MIT license.
Will re-spin.
Neil
>
>
> Martin
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-05-20 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 14:38 [PATCH 00/10] ARM: meson: update with SPDX Licence identifier Neil Armstrong
2019-05-20 14:38 ` [PATCH 01/10] ARM: dts: " Neil Armstrong
2019-05-20 14:38 ` [PATCH 02/10] ARM: dts: meson6-atv1200: " Neil Armstrong
2019-05-20 14:38 ` [PATCH 03/10] ARM: dts: meson6: " Neil Armstrong
2019-05-20 18:05 ` Martin Blumenstingl
2019-05-20 14:38 ` [PATCH 04/10] ARM: dts: meson8-minix-neo-x8: " Neil Armstrong
2019-05-20 14:38 ` [PATCH 05/10] ARM: dts: meson8: " Neil Armstrong
2019-05-20 18:04 ` Martin Blumenstingl
2019-05-20 14:38 ` [PATCH 06/10] ARM: dts: meson8b-mxq: " Neil Armstrong
2019-05-20 14:38 ` [PATCH 07/10] ARM: dts: meson8b-odroidc1: " Neil Armstrong
2019-05-20 14:38 ` [PATCH 08/10] ARM: dts: meson8b: " Neil Armstrong
2019-05-20 18:03 ` Martin Blumenstingl
2019-05-21 20:17 ` Kevin Hilman
2019-05-20 14:38 ` [PATCH 09/10] ARM: debug: meson.S: " Neil Armstrong
2019-05-20 14:38 ` [PATCH 10/10] ARM: mach-meson: " Neil Armstrong
2019-05-20 18:06 ` [PATCH 00/10] ARM: meson: " Martin Blumenstingl
2019-05-20 18:34 ` Neil Armstrong [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=5CE2F337.9060207@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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).