From: Randy Dunlap <rdunlap@infradead.org>
To: LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Jiri Kosina <jikos@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>
Subject: [PTCH] x86: APM: fix build warning when PROC_FS is not enabled
Date: Fri, 14 Sep 2018 15:10:29 -0700 [thread overview]
Message-ID: <be39ac12-44c2-4715-247f-4dcc3c525b8b@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Fix build warning in apm_32.c when CONFIG_PROC_FS is not enabled:
../arch/x86/kernel/apm_32.c:1643:12: warning: 'proc_apm_show' defined but not used [-Wunused-function]
static int proc_apm_show(struct seq_file *m, void *v)
Fixes: 3f3942aca6da ("proc: introduce proc_create_single{,_data}")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Jiri Kosina <jikos@kernel.org>
Cc: x86@kernel.org
---
arch/x86/kernel/apm_32.c | 2 ++
1 file changed, 2 insertions(+)
--- linux-next-20180913.orig/arch/x86/kernel/apm_32.c
+++ linux-next-20180913/arch/x86/kernel/apm_32.c
@@ -1640,6 +1640,7 @@ static int do_open(struct inode *inode,
return 0;
}
+#ifdef CONFIG_PROC_FS
static int proc_apm_show(struct seq_file *m, void *v)
{
unsigned short bx;
@@ -1719,6 +1720,7 @@ static int proc_apm_show(struct seq_file
units);
return 0;
}
+#endif
static int apm(void *unused)
{
next reply other threads:[~2018-09-14 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 22:10 Randy Dunlap [this message]
2018-09-15 6:54 ` [PTCH] x86: APM: fix build warning when PROC_FS is not enabled Christoph Hellwig
2018-09-15 8:21 ` [tip:x86/urgent] x86/APM: Fix " tip-bot for Randy Dunlap
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=be39ac12-44c2-4715-247f-4dcc3c525b8b@infradead.org \
--to=rdunlap@infradead.org \
--cc=hch@lst.de \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).