From: Chanwoo Choi <cwchoi00@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
linux-pm@vger.kernel.org
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / devfreq: passive: revert an editing accident in SPDX-License line
Date: Thu, 30 Jun 2022 04:34:05 +0900 [thread overview]
Message-ID: <0f1fd530-7764-a465-0b02-0027fc9a1383@gmail.com> (raw)
In-Reply-To: <20220628053411.22438-1-lukas.bulwahn@gmail.com>
On 22. 6. 28. 14:34, Lukas Bulwahn wrote:
> Commit 26984d9d581e ("PM / devfreq: passive: Keep cpufreq_policy for
> possible cpus") reworked governor_passive.c, and accidently added a
> tab in the first line, i.e., the SPDX-License-Identifier line.
>
> The checkpatch script warns with the SPDX_LICENSE_TAG warning, and hence
> pointed this issue out while investigating checkpatch warnings.
>
> Revert this editing accident. No functional change.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Chanwoo, please pick this minor non-urgent fix to your latest change above.
>
> drivers/devfreq/governor_passive.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/devfreq/governor_passive.c b/drivers/devfreq/governor_passive.c
> index 72c67979ebe1..326482a68986 100644
> --- a/drivers/devfreq/governor_passive.c
> +++ b/drivers/devfreq/governor_passive.c
> @@ -1,4 +1,4 @@
> - // SPDX-License-Identifier: GPL-2.0-only
> +// SPDX-License-Identifier: GPL-2.0-only
> /*
> * linux/drivers/devfreq/governor_passive.c
> *
Applied it. Thanks.
--
Best Regards,
Samsung Electronics
Chanwoo Choi
prev parent reply other threads:[~2022-06-29 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 5:34 Lukas Bulwahn
2022-06-29 19:34 ` Chanwoo Choi [this message]
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=0f1fd530-7764-a465-0b02-0027fc9a1383@gmail.com \
--to=cwchoi00@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=myungjoo.ham@samsung.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
all inboxes | Powered by JetHome®