From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: Mark ACPI table declaration as maybe unused
Date: Wed, 26 Sep 2018 09:13:59 +0200 [thread overview]
Message-ID: <20180926071359.GA22855@kroah.com> (raw)
In-Reply-To: <20180926070208.16924-1-natechancellor@gmail.com>
On Wed, Sep 26, 2018 at 12:02:09AM -0700, Nathan Chancellor wrote:
> Clang emits the following warning:
>
> drivers/staging/rtl8723bs/os_dep/sdio_intf.c:25:36: warning: variable
> 'acpi_ids' is not needed and will not be emitted
> [-Wunneeded-internal-declaration]
> static const struct acpi_device_id acpi_ids[] = {
> ^
> 1 warning generated.
>
> Mark the declaration as maybe unused like a few other instances of this
> construct in the kernel.
>
> Link: https://github.com/ClangBuiltLinux/linux/issues/169
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
> drivers/staging/rtl8723bs/os_dep/sdio_intf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8723bs/os_dep/sdio_intf.c b/drivers/staging/rtl8723bs/os_dep/sdio_intf.c
> index 6d02904de63f..3285bf36291b 100644
> --- a/drivers/staging/rtl8723bs/os_dep/sdio_intf.c
> +++ b/drivers/staging/rtl8723bs/os_dep/sdio_intf.c
> @@ -22,7 +22,7 @@ static const struct sdio_device_id sdio_ids[] =
> { SDIO_DEVICE(0x024c, 0xb723), },
> { /* end: all zeroes */ },
> };
> -static const struct acpi_device_id acpi_ids[] = {
> +static const struct acpi_device_id acpi_ids[] __maybe_unused = {
But it is used. No "maybe" at all here. The MODULE_DEVICE_TABLE()
macro does a functional thing. Why is gcc not reporting an issue with
this and clang is?
thanks,
greg k-h
next prev parent reply other threads:[~2018-09-26 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 7:02 [PATCH] staging: rtl8723bs: Mark ACPI table declaration as maybe unused Nathan Chancellor
2018-09-26 7:13 ` Greg Kroah-Hartman [this message]
2018-09-26 7:41 ` Nathan Chancellor
2018-09-26 17:55 ` Nick Desaulniers
2018-09-26 18:28 ` Nick Desaulniers
2018-09-26 18:39 ` Greg KH
2018-09-26 22:21 ` Nick Desaulniers
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=20180926071359.GA22855@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.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