From: Zeng Heng <zengheng4@huawei.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: <quic_jjohnson@quicinc.com>, <jinqian@android.com>,
<u.kleine-koenig@pengutronix.de>, <jia-cheng.hu@intel.com>,
<alan@linux.intel.com>, <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>, <bobo.shaobowang@huawei.com>
Subject: Re: [PATCH v2] goldfish: Fix unused const variable 'goldfish_pipe_acpi_match'
Date: Thu, 7 Nov 2024 10:29:13 +0800 [thread overview]
Message-ID: <03cdeacb-918f-7ec7-f7d2-75d86e277872@huawei.com> (raw)
In-Reply-To: <ZyuR8blW8IScgNl-@smile.fi.intel.com>
On 2024/11/6 23:57, Andy Shevchenko wrote:
> On Sat, Oct 26, 2024 at 03:01:50PM +0800, Zeng Heng wrote:
>> Fix the following compilation warning:
>>
>> drivers/platform/goldfish/goldfish_pipe.c:925:36: warning:
>> ‘goldfish_pipe_acpi_match’ defined but not used
>> [-Wunused-const-variable=]
>> 925 | static const struct acpi_device_id goldfish_pipe_acpi_match[] = {
>>
>> The complexity of config guards needed for ACPI_PTR() is not worthwhile
>> for the small amount of saved data. So remove the use of ACPI_PTR instead
>> and drop now unneeded linux/acpi.h include.
> ...
>
>> #include <linux/io.h>
>> #include <linux/dma-mapping.h>
>> #include <linux/mm.h>
>> -#include <linux/acpi.h>
> Because header inclusions are unsorted, it's unclear if there is
> mod_devicetable.h included. If not, you should replace acpi.h with
> mod_devicetable.h.
Yes, I checked mod_devicetable.h had been already included in
goldfish_pipe_qemu.c before.
After the patch is applied, the header files included in the source file
are as follows:
~~~
#include <linux/module.h>
#include <linux/mod_devicetable.h>
#include <linux/interrupt.h>
#include <linux/kernel.h>
#include <linux/spinlock.h>
#include <linux/miscdevice.h>
#include <linux/platform_device.h>
#include <linux/poll.h>
#include <linux/sched.h>
#include <linux/bitops.h>
#include <linux/slab.h>
#include <linux/io.h>
#include <linux/dma-mapping.h>
#include <linux/mm.h>
#include <linux/bug.h>
#include "goldfish_pipe_qemu.h"
~~~
Best regards,
Zeng Heng
prev parent reply other threads:[~2024-11-07 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 7:01 Zeng Heng
2024-11-06 15:57 ` Andy Shevchenko
2024-11-07 2:29 ` Zeng Heng [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=03cdeacb-918f-7ec7-f7d2-75d86e277872@huawei.com \
--to=zengheng4@huawei.com \
--cc=alan@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bobo.shaobowang@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=jia-cheng.hu@intel.com \
--cc=jinqian@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=u.kleine-koenig@pengutronix.de \
/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®