From: Finn Thain <fthain@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] macintosh/via-pmu: Fix build failure when CONFIG_INPUT is disabled
Date: Sat, 19 Mar 2022 16:57:23 +1100 (AEDT) [thread overview]
Message-ID: <25cb7e6c-5239-e84d-e73d-848a66a214f@linux-m68k.org> (raw)
In-Reply-To: <f5cebabc-18f9-7e64-ac34-2c7802104aa1@infradead.org>
On Fri, 18 Mar 2022, Randy Dunlap wrote:
>
> Hi Finn,
> It builds without those reported errors, but I do see these warnings
> since the robot-supplied .config file has:
> # CONFIG_PROC_FS is not set
>
>
> CC drivers/macintosh/via-pmu.o
> ../drivers/macintosh/via-pmu.c:897:12: warning: 'pmu_battery_proc_show' defined but not used [-Wunused-function]
> 897 | static int pmu_battery_proc_show(struct seq_file *m, void *v)
> | ^~~~~~~~~~~~~~~~~~~~~
> ../drivers/macintosh/via-pmu.c:871:12: warning: 'pmu_irqstats_proc_show' defined but not used [-Wunused-function]
> 871 | static int pmu_irqstats_proc_show(struct seq_file *m, void *v)
> | ^~~~~~~~~~~~~~~~~~~~~~
> ../drivers/macintosh/via-pmu.c:860:12: warning: 'pmu_info_proc_show' defined but not used [-Wunused-function]
> 860 | static int pmu_info_proc_show(struct seq_file *m, void *v)
> | ^~~~~~~~~~~~~~~~~~
>
I see. I'll send a separate patch for this issue.
next prev parent reply other threads:[~2022-03-19 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 4:18 [PATCH] macintosh/via-pmu: Fix build failure when CONFIG_INPUT is disabled Finn Thain
2022-03-19 4:56 ` Randy Dunlap
2022-03-19 5:57 ` Finn Thain [this message]
2022-03-19 9:24 ` Geert Uytterhoeven
2022-03-20 0:19 ` Finn Thain
-- strict thread matches above, loose matches on Subject: below --
2022-03-21 4:30 Finn Thain
2022-03-21 6:37 ` Christophe Leroy
2022-03-21 8:29 ` Finn Thain
2022-03-21 8:47 ` Geert Uytterhoeven
2022-03-21 9:09 ` Finn Thain
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=25cb7e6c-5239-e84d-e73d-848a66a214f@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rdunlap@infradead.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