From: Steve Twiss <stwiss.opensource@diasemi.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>, Mark Brown <broonie@kernel.org>,
Support Opensource <Support.Opensource@diasemi.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: RE: [PATCH 3/4] input: da9063_onkey: convert header to SPDX
Date: Tue, 26 Mar 2019 09:23:49 +0000 [thread overview]
Message-ID: <VI1PR10MB2352E1F0C929F73D7220A998FE5F0@VI1PR10MB2352.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20190318155728.28365-4-wsa+renesas@sang-engineering.com>
On 18 March 2019 15:57, Wolfram Sang wrote:
> Subject: [PATCH 3/4] input: da9063_onkey: convert header to SPDX
> Covnert the header of the source file to SPDX.
[...]
> +// SPDX-License-Identifier: GPL-2.0+
> /*
> * OnKey device driver for DA9063, DA9062 and DA9061 PMICs
> * Copyright (C) 2015 Dialog Semiconductor Ltd.
[...]
> */
Thanks!
Acked-by: Steve Twiss <stwiss.opensource@diasemi.com>
next prev parent reply other threads:[~2019-03-26 9:24 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
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 [this message]
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=VI1PR10MB2352E1F0C929F73D7220A998FE5F0@VI1PR10MB2352.EURPRD10.PROD.OUTLOOK.COM \
--to=stwiss.opensource@diasemi.com \
--cc=Support.Opensource@diasemi.com \
--cc=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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).