From: Yuehaibing <yuehaibing@huawei.com>
To: "Kaneda, Erik" <erik.kaneda@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Moore, Robert" <robert.moore@intel.com>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"open list:ACPI COMPONENT ARCHITECTURE (ACPICA)"
<devel@acpica.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] ACPICA: Make acpi_protocol_lengths static
Date: Tue, 31 Mar 2020 11:29:08 +0800 [thread overview]
Message-ID: <81c23927-e3eb-dd97-6b9d-5e91d19a61b8@huawei.com> (raw)
In-Reply-To: <CY4PR11MB171942777865293C74EF1D9AF0CB0@CY4PR11MB1719.namprd11.prod.outlook.com>
On 2020/3/31 1:52, Kaneda, Erik wrote:
>
>
>> -----Original Message-----
>> From: linux-acpi-owner@vger.kernel.org <linux-acpi-
>> owner@vger.kernel.org> On Behalf Of Rafael J. Wysocki
>> Sent: Saturday, March 28, 2020 2:14 AM
>> To: YueHaibing <yuehaibing@huawei.com>; Moore, Robert
>> <robert.moore@intel.com>; Kaneda, Erik <erik.kaneda@intel.com>
>> Cc: Wysocki, Rafael J <rafael.j.wysocki@intel.com>; Len Brown
>> <lenb@kernel.org>; ACPI Devel Maling List <linux-acpi@vger.kernel.org>;
>> open list:ACPI COMPONENT ARCHITECTURE (ACPICA) <devel@acpica.org>;
>> Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
>> Subject: Re: [PATCH -next] ACPICA: Make acpi_protocol_lengths static
>>
>> On Sat, Mar 28, 2020 at 4:47 AM YueHaibing <yuehaibing@huawei.com>
>> wrote:
>>>
>>> Fix sparse warning:
>>>
>>> drivers/acpi/acpica/exfield.c:25:10: warning:
>>> symbol 'acpi_protocol_lengths' was not declared. Should it be static?
>
> I don’t understand what sparse is trying to say here. This variable is declared in exfield.c...
> Could you provide more details on this sparse warning?
This is sparse -Wdel option's job, see man manual:
-Wdecl Warn about any non-static variable or function definition that
has no previous declaration.
Private symbols (functions and variables) internal to a given
source file should use static, to allow additional compiler
optimizations, allow detection of unused symbols, and prevent
other code from relying on these internal symbols. Public
symbols used by other source files will need declarations
visible to those other source files, such as in a header file.
All declarations should fall into one of these two categories.
Thus, with -Wdecl, Sparse warns about any symbol definition
with neither static nor a declaration. To fix this warning,
declare private symbols static, and ensure that the files
defining public symbols have the symbol declarations available
first (such as by including the appropriate header file).
>
> Erik
>
>>>
>>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>>
>> Bob, Erik, I'm leaving this one to you.
>>
>>> ---
>>> drivers/acpi/acpica/exfield.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/acpi/acpica/exfield.c
>>> b/drivers/acpi/acpica/exfield.c index e85eb31e5075..3323a2ba6a31
>>> 100644
>>> --- a/drivers/acpi/acpica/exfield.c
>>> +++ b/drivers/acpi/acpica/exfield.c
>>> @@ -22,7 +22,7 @@ ACPI_MODULE_NAME("exfield")
>>> */
>>> #define ACPI_INVALID_PROTOCOL_ID 0x80
>>> #define ACPI_MAX_PROTOCOL_ID 0x0F
>>> -const u8 acpi_protocol_lengths[] = {
>>> +static const u8 acpi_protocol_lengths[] = {
>>> ACPI_INVALID_PROTOCOL_ID, /* 0 - reserved */
>>> ACPI_INVALID_PROTOCOL_ID, /* 1 - reserved */
>>> 0x00, /* 2 - ATTRIB_QUICK */
>>> --
>>> 2.17.1
>>>
>>>
next prev parent reply other threads:[~2020-03-31 3:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 3:47 YueHaibing
2020-03-28 9:14 ` Rafael J. Wysocki
2020-03-30 17:52 ` Kaneda, Erik
2020-03-31 3:29 ` Yuehaibing [this message]
2020-03-31 17:34 ` Kaneda, Erik
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=81c23927-e3eb-dd97-6b9d-5e91d19a61b8@huawei.com \
--to=yuehaibing@huawei.com \
--cc=devel@acpica.org \
--cc=erik.kaneda@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.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®