From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: <torvalds@transmeta.com>, <ralf@gnu.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH] reduce CONFIG_INPUT as forward symbol (with diff)
Date: Mon, 26 Aug 2002 09:28:08 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33L2.0208260923510.25879-100000@dragon.pdx.osdl.net> (raw)
In-Reply-To: <20020826093428.B2524@ucw.cz>
[repost with patch this time]
Hi,
I've been using gcml2 from Greg Banks to look at CONFIG_
variable dependencies in config.in files.
By moving drivers/input/config.in before drivers/char/Config.in
and drivers/usb/Config.in for arch/alpha and arch/mips(64),
several (7) instances of this message:
forward declared symbol "CONFIG_INPUT" used in dependency list
and (6) instances of this one:
forward declared symbol "CONFIG_SOUND_GAMEPORT" used in
dependency list
can be removed. (Yes, the latter one is for OSS drivers,
so it's not so important.)
It also adds one forward dependency for a USB joystick
in the input subsystem [still only for alpha and mips(64)].
Most other arches are already like this.
This patch is to 2.5.31-bk7 (jgarzik's latest snapshot).
Please apply.
On Mon, 26 Aug 2002, Vojtech Pavlik wrote:
|
| I'd like to take a look at the patch - both the symbols are from the
| input drivers. Where can I find it? And what was the exact problem?
Yes, I forgot the patch...too late last night.
It's now below.
This patch just makes alpha and mips(64) use the same ordering
for "source drivers/input/Config.in" that most other arches use,
so that there are fewer forward references to CONFIG_INPUT.
Please apply.
--
~Randy
--- ./arch/alpha/config.in.inputt Sun Aug 25 21:14:09 2002
+++ ./arch/alpha/config.in Sun Aug 25 21:37:33 2002
@@ -335,6 +335,7 @@
fi
endmenu
+source drivers/input/Config.in
source drivers/char/Config.in
source drivers/char/Config-tape.in
@@ -371,7 +372,6 @@
endmenu
source drivers/usb/Config.in
-source drivers/input/Config.in
source net/bluetooth/Config.in
--- ./arch/mips64/config.in.inputt Sun Aug 25 21:14:09 2002
+++ ./arch/mips64/config.in Sun Aug 25 22:08:45 2002
@@ -186,6 +186,8 @@
fi
endmenu
+source drivers/input/Config.in
+
source drivers/char/Config.in
source drivers/char/Config-tape.in
@@ -229,7 +231,6 @@
fi
source drivers/usb/Config.in
-source drivers/input/Config.in
mainmenu_option next_comment
comment 'Kernel hacking'
--- ./arch/mips/config.in.inputt Sun Aug 25 21:14:09 2002
+++ ./arch/mips/config.in Sun Aug 25 22:04:30 2002
@@ -395,6 +395,8 @@
fi
endmenu
+source drivers/input/Config.in
+
source drivers/char/Config.in
source drivers/char/Config-tape.in
@@ -482,7 +484,6 @@
fi
source drivers/usb/Config.in
-source drivers/input/Config.in
mainmenu_option next_comment
comment 'Kernel hacking'
next prev parent reply other threads:[~2002-08-26 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 5:59 [PATCH] reduce CONFIG_INPUT as forward symbol Randy.Dunlap
2002-08-26 7:34 ` Vojtech Pavlik
2002-08-26 16:28 ` Randy.Dunlap [this message]
2002-08-26 16:33 ` [PATCH] reduce CONFIG_INPUT as forward symbol (with diff) Vojtech Pavlik
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.LNX.4.33L2.0208260923510.25879-100000@dragon.pdx.osdl.net \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@gnu.org \
--cc=torvalds@transmeta.com \
--cc=vojtech@suse.cz \
/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).