From: Stephen Boyd <sboyd@kernel.org>
To: Andreas Färber <afaerber@suse.de>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Nishad Kamdar <nishadkamdar@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Uwe Kleine-König <u.kleine-koenig@pengutronix.de>,
Joe Perches <joe@perches.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: actions: Use the correct style for SPDX License Identifier
Date: Wed, 01 May 2019 13:02:56 -0700 [thread overview]
Message-ID: <155674097693.168659.16500258534708901697@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20190501070707.GA5619@nishad>
Quoting Nishad Kamdar (2019-05-01 00:07:11)
> This patch corrects the SPDX License Identifier style
> in header files related to Clock Drivers for Actions Semi Socs.
> For C header files Documentation/process/license-rules.rst
> mandates C-like comments (opposed to C source files where
> C++ style should be used)
>
> Changes made by using a script provided by Joe Perches here:
> https://lkml.org/lkml/2019/2/7/46
>
> Suggested-by: Joe Perches <joe@perches.com>
> Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
> ---
Applied to clk-next
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-01 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 7:07 [PATCH] clk: actions: Use the correct style for SPDX License Identifier Nishad Kamdar
2019-05-01 7:07 ` Nishad Kamdar
2019-05-01 20:02 ` Stephen Boyd [this message]
2019-05-01 20:20 ` Andreas Färber
2019-05-01 20:20 ` Andreas Färber
2019-05-02 7:07 ` Greg Kroah-Hartman
2019-05-02 7:07 ` Greg Kroah-Hartman
2019-05-02 10:25 ` Andreas Färber
2019-05-02 10:25 ` Andreas Färber
2019-05-02 10:38 ` Greg Kroah-Hartman
2019-05-02 10:38 ` Greg Kroah-Hartman
2019-05-02 10:45 ` Andreas Färber
2019-05-02 10:45 ` Andreas Färber
2019-05-02 11:28 ` Greg Kroah-Hartman
2019-05-02 11:28 ` 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=155674097693.168659.16500258534708901697@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=afaerber@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mturquette@baylibre.com \
--cc=nishadkamdar@gmail.com \
--cc=u.kleine-koenig@pengutronix.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 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.