mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: torvalds@transmeta.com, ralf@gnu.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reduce CONFIG_INPUT as forward symbol
Date: Mon, 26 Aug 2002 09:34:28 +0200	[thread overview]
Message-ID: <20020826093428.B2524@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0208252243130.23948-100000@dragon.pdx.osdl.net>; from rddunlap@osdl.org on Sun, Aug 25, 2002 at 10:59:47PM -0700

On Sun, Aug 25, 2002 at 10:59:47PM -0700, Randy.Dunlap wrote:
> 
> 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.

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?

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-08-26  7:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26  5:59 Randy.Dunlap
2002-08-26  7:34 ` Vojtech Pavlik [this message]
2002-08-26 16:28   ` [PATCH] reduce CONFIG_INPUT as forward symbol (with diff) Randy.Dunlap
2002-08-26 16:33     ` 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=20020826093428.B2524@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@gnu.org \
    --cc=rddunlap@osdl.org \
    --cc=torvalds@transmeta.com \
    /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®