From: Geert Uytterhoeven <geert@linux-m68k•org>
To: Mikael Starvik <starvik@axis•com>,
Jesper Nilsson <jesper.nilsson@axis•com>
Cc: linux-cris-kernel@axis•com, linux-next@vger•kernel.org,
linux-kernel@vger•kernel.org,
Geert Uytterhoeven <geert@linux-m68k•org>
Subject: [PATCH -next] cris: cpuinfo_op should depend on CONFIG_PROC_FS
Date: Sun, 2 Mar 2014 11:34:39 +0100 [thread overview]
Message-ID: <1393756479-12530-1-git-send-email-geert@linux-m68k.org> (raw)
Now allnoconfig started disabling CONFIG_PROC_FS:
arch/cris/kernel/built-in.o:(.rodata+0xc): undefined reference to `show_cpuinfo'
make: *** [vmlinux] Error 1
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k•org>
---
http://kisskb.ellerman.id.au/kisskb/buildresult/10665698/
arch/cris/kernel/setup.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/cris/kernel/setup.c b/arch/cris/kernel/setup.c
index 32c3d248868e..905b70ea9939 100644
--- a/arch/cris/kernel/setup.c
+++ b/arch/cris/kernel/setup.c
@@ -165,6 +165,7 @@ void __init setup_arch(char **cmdline_p)
strcpy(init_utsname()->machine, cris_machine_name);
}
+#ifdef CONFIG_PROC_FS
static void *c_start(struct seq_file *m, loff_t *pos)
{
return *pos < nr_cpu_ids ? (void *)(int)(*pos + 1) : NULL;
@@ -188,6 +189,7 @@ const struct seq_operations cpuinfo_op = {
.stop = c_stop,
.show = show_cpuinfo,
};
+#endif /* CONFIG_PROC_FS */
static int __init topology_init(void)
{
--
1.7.9.5
next reply other threads:[~2014-03-02 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 10:34 Geert Uytterhoeven [this message]
2014-03-03 0:16 ` [PATCH -next] cris: cpuinfo_op should depend on CONFIG_PROC_FS Stephen Rothwell
2014-03-03 2:09 ` Josh Triplett
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=1393756479-12530-1-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k$(echo .)org \
--cc=jesper.nilsson@axis$(echo .)com \
--cc=linux-cris-kernel@axis$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=starvik@axis$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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