mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Roman Zippel" <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Fwd: Using select in boolean dependents of a tristate symbol
Date: Thu, 13 Jul 2006 15:35:27 -0400	[thread overview]
Message-ID: <d120d5000607131235r5cc9b558xfd04a1f3118d8124@mail.gmail.com> (raw)
In-Reply-To: <d120d5000607131232i74dfdb9t1a132dfc5dd32bc4@mail.gmail.com>

[Argh.. resending to correct LKML address]

Roman,

Question for you as Kconfig maintainer - I have a module (HID) that
has a few sub-options. Now HID can be built as a module but
sub-options are suimple booleans. Some of these sub-options will
depend on a common code which is moved out of HID driver. Now I want
to use "select" like this:

 config THRUSTMASTER_FF
       bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)"
       depends on HID_FF && EXPERIMENTAL
+       select INPUT_FF_MEMLESS
       help
         Say Y here if you have a THRUSTMASTER FireStore Dual Power 2,
         and want to enable force feedback support for it.

Unfortunately this forces INPUT_FF_MEMLESS to always be built-in,
although if HID is a module it could be a module as well. Do you have
any suggestions as to how allow INPUT_FF_MEMLESS to be compiled as a
module?

Thanks!

--
Dmitry


-- 
Dmitry

       reply	other threads:[~2006-07-13 19:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d120d5000607131232i74dfdb9t1a132dfc5dd32bc4@mail.gmail.com>
2006-07-13 19:35 ` Dmitry Torokhov [this message]
2006-07-13 22:58   ` Roman Zippel
2006-07-14  2:31     ` Dmitry Torokhov
2006-07-14  9:20       ` Roman Zippel
2006-07-19 20:17         ` Dmitry Torokhov
2006-07-19 20:41           ` Valdis.Kletnieks
2006-07-19 20:50             ` Dmitry Torokhov
2006-07-27  0:42           ` Roman Zippel
2006-07-27  1:05             ` Dmitry Torokhov

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=d120d5000607131235r5cc9b558xfd04a1f3118d8124@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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®