From: Mark Brown <broonie@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>,
Support Opensource <support.opensource@diasemi.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 2/4] regulator: da9063: convert header to SPDX
Date: Tue, 19 Mar 2019 12:56:12 +0000 [thread overview]
Message-ID: <20190319125612.GB5514@sirena.org.uk> (raw)
In-Reply-To: <20190318155728.28365-3-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
On Mon, Mar 18, 2019 at 04:57:25PM +0100, Wolfram Sang wrote:
> index 2b0c7a85306a..42dca1cac077 100644
> --- a/drivers/regulator/da9063-regulator.c
> +++ b/drivers/regulator/da9063-regulator.c
> @@ -1,4 +1,4 @@
> -
> +// SPDX-License-Identifier: GPL-2.0+
> /*
> * Regulator driver for DA9063 PMIC series
> *
Please make the entire comment block C++ so this looks more intentional.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-03-19 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 15:57 [PATCH 0/4] da9063: convert to SPDX Wolfram Sang
2019-03-18 15:57 ` [PATCH 1/4] mfd: da9063: convert headers " Wolfram Sang
2019-03-19 12:10 ` Simon Horman
2019-03-27 15:03 ` Steve Twiss
2019-04-03 7:46 ` Lee Jones
2019-03-18 15:57 ` [PATCH 2/4] regulator: da9063: convert header " Wolfram Sang
2019-03-19 12:10 ` Simon Horman
2019-03-19 12:56 ` Mark Brown [this message]
2019-03-25 20:32 ` Wolfram Sang
2019-03-18 15:57 ` [PATCH 3/4] input: da9063_onkey: " Wolfram Sang
2019-03-19 12:09 ` Simon Horman
2019-03-26 9:23 ` Steve Twiss
2019-03-18 15:57 ` [PATCH 4/4] rtc: da9063: " Wolfram Sang
2019-03-19 12:10 ` Simon Horman
2019-03-20 19:19 ` Alexandre Belloni
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=20190319125612.GB5514@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=support.opensource@diasemi.com \
--cc=wsa+renesas@sang-engineering.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).