From: Hans de Goede <hdegoede@redhat.com>
To: Tom Rix <trix@redhat.com>, djrscally@gmail.com, markgross@kernel.org
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: int3472/discrete: set variable skl_int3472_regulator_second_sensor storage-class-specifier to static
Date: Tue, 11 Jul 2023 11:44:06 +0200 [thread overview]
Message-ID: <d9c9d8d0-3b1f-8f8e-5fbf-84448c3a20e5@redhat.com> (raw)
In-Reply-To: <20230702134419.3438361-1-trix@redhat.com>
Hi,
On 7/2/23 15:44, Tom Rix wrote:
> smatch reports
> drivers/platform/x86/intel/int3472/clk_and_regulator.c:263:28: warning: symbol
> 'skl_int3472_regulator_second_sensor' was not declared. Should it be static?
>
> This variable is only used in its defining file, so it should be static.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> drivers/platform/x86/intel/int3472/clk_and_regulator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/intel/int3472/clk_and_regulator.c b/drivers/platform/x86/intel/int3472/clk_and_regulator.c
> index 61aeca804ba2..ef4b3141efcd 100644
> --- a/drivers/platform/x86/intel/int3472/clk_and_regulator.c
> +++ b/drivers/platform/x86/intel/int3472/clk_and_regulator.c
> @@ -260,7 +260,7 @@ static_assert(ARRAY_SIZE(skl_int3472_regulator_map_supplies) ==
> * This DMI table contains the name of the second sensor. This is used to add
> * entries for the second sensor to the supply_map.
> */
> -const struct dmi_system_id skl_int3472_regulator_second_sensor[] = {
> +static const struct dmi_system_id skl_int3472_regulator_second_sensor[] = {
> {
> /* Lenovo Miix 510-12IKB */
> .matches = {
Thank you for your patch, I've applied this patch to my fixes
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=fixes
Note it will show up in my fixes branch once I've pushed my
local branch there, which might take a while.
I will include this patch in my next fixes pull-req to Linus
for the current kernel development cycle.
Regards,
Hans
prev parent reply other threads:[~2023-07-11 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 13:44 Tom Rix
2023-07-11 9:44 ` Hans de Goede [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=d9c9d8d0-3b1f-8f8e-5fbf-84448c3a20e5@redhat.com \
--to=hdegoede@redhat.com \
--cc=djrscally@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=trix@redhat.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®