From: Shuah Khan <skhan@linuxfoundation.org>
To: Meng Li <li.meng@amd.com>, Huang Rui <ray.huang@amd.com>,
linux-kselftest@vger.kernel.org
Cc: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Nathan Fontenot <nathan.fontenot@amd.com>,
Deepak Sharma <deepak.sharma@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Shimmer Huang <shimmer.huang@amd.com>,
Perry Yuan <Perry.Yuan@amd.com>,
Xiaojian Du <Xiaojian.Du@amd.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] cpufreq: amd-pstate: fix spdxcheck warnings for amd-pstate-ut.c
Date: Wed, 16 Nov 2022 08:39:39 -0700 [thread overview]
Message-ID: <2ab19d48-57e2-ba0e-6d36-431acc26dec3@linuxfoundation.org> (raw)
In-Reply-To: <20221114054037.2962372-1-li.meng@amd.com>
On 11/13/22 22:40, Meng Li wrote:
> spdxcheck warnings: (new ones prefixed by >>)
>>> drivers/cpufreq/amd-pstate-ut.c: 1:28 Invalid License ID:
> GPL-1.0-or-later
> drivers/spi/spi-gxp.c: 1:35 Invalid token: =or-later
>
> Signed-off-by: Meng Li <li.meng@amd.com>
> Reported-by: kernel test robot <lkp@intel.com>
> ---
> drivers/cpufreq/amd-pstate-ut.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/amd-pstate-ut.c b/drivers/cpufreq/amd-pstate-ut.c
> index e4a5b4d90f83..7f3fe2048981 100644
> --- a/drivers/cpufreq/amd-pstate-ut.c
> +++ b/drivers/cpufreq/amd-pstate-ut.c
> @@ -1,4 +1,4 @@
> -// SPDX-License-Identifier: GPL-1.0-or-later
> +// SPDX-License-Identifier: GPL-2.0-or-later
> /*
> * AMD Processor P-state Frequency Driver Unit Test
> *
Thank you. Applied to linux-kselftest next for Linux 6.2-rc1
thanks,
-- Shuah
prev parent reply other threads:[~2022-11-16 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 5:40 [PATCH] cpufreq: amd-pstate: fix spdxcheck warnings for amd-pstate-ut.c Meng Li
2022-11-16 15:39 ` Shuah Khan [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=2ab19d48-57e2-ba0e-6d36-431acc26dec3@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Perry.Yuan@amd.com \
--cc=Xiaojian.Du@amd.com \
--cc=alexander.deucher@amd.com \
--cc=bp@alien8.de \
--cc=deepak.sharma@amd.com \
--cc=li.meng@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mario.limonciello@amd.com \
--cc=nathan.fontenot@amd.com \
--cc=rafael.j.wysocki@intel.com \
--cc=ray.huang@amd.com \
--cc=shimmer.huang@amd.com \
--cc=viresh.kumar@linaro.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