All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH 1/4] drivers: base: regmap: add proper SPDX identifiers on files that did not have them.
Date: Thu, 25 Apr 2019 20:05:07 +0200	[thread overview]
Message-ID: <20190425180507.GA8998@kroah.com> (raw)
In-Reply-To: <20190403033227.GG2059@sirena.org.uk>

On Wed, Apr 03, 2019 at 10:32:27AM +0700, Mark Brown wrote:
> On Tue, Apr 02, 2019 at 03:32:00PM +0200, Greg Kroah-Hartman wrote:
> 
> > --- a/drivers/base/regmap/regcache-flat.c
> > +++ b/drivers/base/regmap/regcache-flat.c
> > @@ -1,13 +1,10 @@
> > +// SPDX-License-Identifier: GPL-2.0
> >  /*
> 
> Please make the whole header a C++ header so that things look more
> consistent and intentional.

Ok, fair enough, will do so now.

greg k-h

  parent reply	other threads:[~2019-04-25 18:05 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 [this message]
2019-04-25 18:06 ` [PATCH v2] " Greg Kroah-Hartman
2019-04-25 18:52   ` Mark Brown
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=20190425180507.GA8998@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.