From: Jaswinder Singh Rajput <jaswinder@infradead.org>
To: Ingo Molnar <mingo@elte.hu>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
sam@ravnborg.org, harvey.harrison@gmail.com, gorcunov@gmail.com,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH -tip] nubus.h: extern's make no sense in userspace
Date: Tue, 13 Jan 2009 13:18:26 +0530 [thread overview]
Message-ID: <1231832906.3212.24.camel@jaswinder.satnam> (raw)
Impact: cleanup, Impact: fix 3 make headers_check warnings:
usr/include/linux/nubus.h:298: extern's make no sense in userspace
usr/include/linux/nubus.h:300: extern's make no sense in userspace
usr/include/linux/nubus.h:304: extern's make no sense in userspace
Also moved nubus_scan_bus() in __KERNEL__
Also removed obsolete get_nubus_list()
Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
---
include/linux/nubus.h | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/include/linux/nubus.h b/include/linux/nubus.h
index bd31554..9f54a23 100644
--- a/include/linux/nubus.h
+++ b/include/linux/nubus.h
@@ -297,6 +297,7 @@ struct nubus_dev {
struct nubus_board* board;
};
+#ifdef __KERNEL__
/* This is all NuBus devices (used to find devices later on) */
extern struct nubus_dev* nubus_devices;
/* This is all NuBus cards */
@@ -305,7 +306,7 @@ extern struct nubus_board* nubus_boards;
/* Generic NuBus interface functions, modelled after the PCI interface */
void nubus_scan_bus(void);
extern void nubus_proc_init(void);
-int get_nubus_list(char *buf);
+#endif /* __KERNEL__ */
int nubus_proc_attach_device(struct nubus_dev *dev);
int nubus_proc_detach_device(struct nubus_dev *dev);
/* If we need more precision we can add some more of these */
--
1.5.6.6
next reply other threads:[~2009-01-13 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 7:48 Jaswinder Singh Rajput [this message]
2009-01-13 9:03 ` Geert Uytterhoeven
2009-01-14 20:04 ` Harvey Harrison
2009-01-14 20:10 ` Sam Ravnborg
2009-01-14 20:13 ` Harvey Harrison
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=1231832906.3212.24.camel@jaswinder.satnam \
--to=jaswinder@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gorcunov@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®