From: Florian Fainelli <f.fainelli@gmail.com>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>,
tsbogend@alpha.franken.de, jonas.gorski@gmail.com,
bcm-kernel-feedback-list@broadcom.com,
linux-mips@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/5] MIPS: BCM63xx: switch to SPDX license identifier
Date: Wed, 12 Aug 2020 07:24:34 -0700 [thread overview]
Message-ID: <aeb79263-896b-54a1-4142-783bb32d4c16@gmail.com> (raw)
In-Reply-To: <20200812075235.366864-6-noltari@gmail.com>
On 8/12/2020 12:52 AM, Álvaro Fernández Rojas wrote:
> Use SPDX license indentifier instead of local reference to COPYING.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2020-08-12 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 7:52 [PATCH v4 0/5] MIPS: BCM63xx: board improvements Álvaro Fernández Rojas
2020-08-12 7:52 ` [PATCH v4 1/5] MIPS: BCM63xx: remove duplicated new lines Álvaro Fernández Rojas
2020-08-12 7:52 ` [PATCH v4 2/5] MIPS: BCM63xx: remove EHCI from BCM6348 boards Álvaro Fernández Rojas
2020-08-12 13:04 ` Philippe Mathieu-Daudé
2020-08-12 7:52 ` [PATCH v4 3/5] MIPS: BCM63xx: enable EHCI for DWV-S0 board Álvaro Fernández Rojas
2020-08-12 13:05 ` Philippe Mathieu-Daudé
2020-08-12 7:52 ` [PATCH v4 4/5] MIPS: BCM63xx: refactor board declarations Álvaro Fernández Rojas
2020-08-13 13:11 ` Philippe Mathieu-Daudé
2020-08-12 7:52 ` [PATCH v4 5/5] MIPS: BCM63xx: switch to SPDX license identifier Álvaro Fernández Rojas
2020-08-12 14:24 ` Florian Fainelli [this message]
2020-08-17 11:16 ` [PATCH v4 0/5] MIPS: BCM63xx: board improvements Thomas Bogendoerfer
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=aeb79263-896b-54a1-4142-783bb32d4c16@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=tsbogend@alpha.franken.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;
as well as URLs for NNTP newsgroup(s).