From: "Noah J. Misch" <noah@caltech.edu>
To: rddunlap@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: patches for PROC_FS=n (2.6.0-test7)
Date: Fri, 10 Oct 2003 16:06:29 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.58.0310101519330.9806@inky> (raw)
> drivers/char/toshiba.c and
> net/atm/clip.c don't build if PROC_FS=n.
> Patches for them are available at:
> http://developer.osdl.org/rddunlap/patches/toshiba_inline_260t7.patch
Consider the patch at the bottom of this message instead. The tosh_get_info
function is really internal to drivers/char/toshiba.c, so instead I changed it
to static in that file and completely removed the prototype in toshiba.h.
BTW, both your patch (I think) and mine also solve a duplicate symbol problem -
see the ChangeSet log for details.
> http://developer.osdl.org/rddunlap/patches/atmprocfs_260t7.patch
Cool.
> There are several other drivers/protocols that don't build
> with PROC_FS=n, like arlan, siimage, ipx, llc, and bluetooth.
I put in a patch for ipx yesterday, and I have patches for siimage and llc
pretty much ready to go. I noticed the others but I have not done much.
Thanks,
Noah
Toshiba patch:
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.1344 -> 1.1345
# include/linux/toshiba.h 1.3 -> 1.4
# drivers/char/toshiba.c 1.11 -> 1.12
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/10/10 noah@caltech.edu 1.1345
# Remove the prototypes for tosh_get_info from include/linux/toshiba.h and
# make the function's definition in drivers/char/toshiba.c static. This
# function is specific to toshiba.c, so no other file needs the prototype.
#
# This allows drivers/char/toshiba.c to compile with CONFIG_PROC_FS=n and
# allows one to link more than one driver that includes toshiba.h into the
# kernel at the same time without a multiple declaration; for example, both
# drivers/char/toshiba.c and drivers/video/neofb.c.
# --------------------------------------------
#
diff -Nru a/drivers/char/toshiba.c b/drivers/char/toshiba.c
--- a/drivers/char/toshiba.c Fri Oct 10 18:50:17 2003
+++ b/drivers/char/toshiba.c Fri Oct 10 18:50:17 2003
@@ -292,7 +292,7 @@
* Print the information for /proc/toshiba
*/
#ifdef CONFIG_PROC_FS
-int tosh_get_info(char *buffer, char **start, off_t fpos, int length)
+static int tosh_get_info(char *buffer, char **start, off_t fpos, int length)
{
char *temp;
int key;
diff -Nru a/include/linux/toshiba.h b/include/linux/toshiba.h
--- a/include/linux/toshiba.h Fri Oct 10 18:50:17 2003
+++ b/include/linux/toshiba.h Fri Oct 10 18:50:17 2003
@@ -33,13 +33,4 @@
unsigned int edi __attribute__ ((packed));
} SMMRegisters;
-#ifdef CONFIG_PROC_FS
-static int tosh_get_info(char *, char **, off_t, int);
-#else /* !CONFIG_PROC_FS */
-inline int tosh_get_info(char *buffer, char **start, off_t fpos, int lenght)
-{
- return 0;
-}
-#endif /* CONFIG_PROC_FS */
-
#endif
next reply other threads:[~2003-10-10 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 23:06 Noah J. Misch [this message]
2003-10-11 2:45 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2003-10-10 21:16 Randy.Dunlap
2003-10-11 19:08 ` David S. Miller
2003-10-11 19:40 ` Sam Ravnborg
2003-10-11 19:40 ` David S. Miller
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=Pine.GSO.4.58.0310101519330.9806@inky \
--to=noah@caltech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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®