From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Noah J. Misch" <noah@caltech.edu>
Cc: netdev@oss.sgi.com, davem@redhat.com, elmer@ylenurme.ee,
Elmer.Joandi@ut.ee
Subject: Re: patches for PROC_FS=n (2.6.0-test7)
Date: Sun, 12 Oct 2003 20:13:16 -0700 [thread overview]
Message-ID: <20031012201316.7ecf73c8.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0310101519330.9806@inky>
On Fri, 10 Oct 2003 16:06:29 -0700 (PDT) "Noah J. Misch" <noah@caltech.edu> wrote:
| > There are several other drivers/protocols that don't build
| > with PROC_FS=n, like arlan, siimage, ipx, llc, and bluetooth.
Here's a patch for the wireless/arlan driver for PROC_FS=n.
Currently it defines both a function and a macro for
init_arlan_proc() if PROC_FS=n. This causes a bunch of
compile-time errors.
It looks to me like it should always call the init_arlan_proc()
(and cleanup_arlan_proc()) functions since it inits some sysctl tables.
Or am I misunderstanding it?
Thanks,
--
~Randy
patch_name: arlan_noprocfs.patch
patch_version: 2003-10-12.19:46:24
author: Randy.Dunlap <rddunlap@osdl.org>
description: use init_arlan_proc() for sysctl inits
product: Linux
product_versions: 2.6.0-test7
diffstat: =
drivers/net/wireless/arlan.h | 5 -----
1 files changed, 5 deletions(-)
diff -Naur ./drivers/net/wireless/arlan.h~arlanprocfs ./drivers/net/wireless/arlan.h
--- ./drivers/net/wireless/arlan.h~arlanprocfs 2003-10-08 12:24:08.000000000 -0700
+++ ./drivers/net/wireless/arlan.h 2003-10-12 19:45:46.000000000 -0700
@@ -39,13 +39,8 @@
#define ARLAN_RCV_PROMISC 1
#define ARLAN_RCV_CONTROL 2
-#ifdef CONFIG_PROC_FS
extern int init_arlan_proc(void);
extern void cleanup_arlan_proc(void);
-#else
-#define init_arlan_proc() (0)
-#define cleanup_arlan_proc() do { } while (0);
-#endif
extern struct net_device *arlan_device[MAX_ARLANS];
extern int arlan_debug;
next prev parent reply other threads:[~2003-10-13 3:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.58.0310101519330.9806@inky>
2003-10-13 2:17 ` patches for PROC_FS=n (2.6.0-test7) Randy.Dunlap
2003-10-14 5:17 ` Noah J. Misch
2003-10-13 3:13 ` Randy.Dunlap [this message]
2003-10-13 11:31 ` Elmer
2003-10-13 14:49 ` Randy.Dunlap
2003-10-14 5:52 ` Noah J. Misch
2003-10-14 6:12 ` Randy.Dunlap
2003-10-14 8:39 ` Elmer
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
2003-10-12 3:24 ` 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=20031012201316.7ecf73c8.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=Elmer.Joandi@ut.ee \
--cc=davem@redhat.com \
--cc=elmer@ylenurme.ee \
--cc=netdev@oss.sgi.com \
--cc=noah@caltech.edu \
/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).