From: Mark Brown <broonie@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v2] drivers: base: regmap: add proper SPDX identifiers on files that did not have them.
Date: Thu, 25 Apr 2019 19:52:25 +0100 [thread overview]
Message-ID: <20190425185225.GI23183@sirena.org.uk> (raw)
In-Reply-To: <20190425180618.GB8998@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
On Thu, Apr 25, 2019 at 08:06:18PM +0200, Greg Kroah-Hartman wrote:
> There were a few files in the regmap code that did not have SPDX
> identifiers on them, so fix that up. At the same time, remove the "free
> form" text that specified the license of the file, as that is impossible
> for any tool to properly parse.
Please use subject lines matching the style for the subsystem. This
makes it easier for people to identify relevant patches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-25 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 13:32 [PATCH 1/4] drivers: base: regmap: add proper SPDX identifiers on files that did not have them Greg Kroah-Hartman
2019-04-02 13:32 ` [PATCH 2/4] drivers: base: power: " Greg Kroah-Hartman
2019-04-02 13:32 ` [PATCH 3/4] drivers: base: firmware_loader: " Greg Kroah-Hartman
2019-04-02 13:32 ` [PATCH 4/4] drivers: base: test: add proper SPDX identifier to Makefile Greg Kroah-Hartman
2019-04-03 3:32 ` [PATCH 1/4] drivers: base: regmap: add proper SPDX identifiers on files that did not have them Mark Brown
2019-04-04 18:03 ` Greg Kroah-Hartman
2019-04-25 18:05 ` Greg Kroah-Hartman
2019-04-25 18:06 ` [PATCH v2] " Greg Kroah-Hartman
2019-04-25 18:52 ` Mark Brown [this message]
2019-04-25 19:04 ` Greg Kroah-Hartman
2019-04-25 19:04 ` [PATCH v3] " Greg Kroah-Hartman
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=20190425185225.GI23183@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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).