From: Tony Breeds <tony@bakeyournoodle•com>
To: Jiri Kosina <jkosina@suse•cz>
Cc: Jeremy Fitzhardinge <jeremy@goop•org>,
LinuxPPC-dev <linuxppc-dev@lists•ozlabs.org>,
Linux Kernel ML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next bad Kconfig for drivers/hid
Date: Mon, 12 Dec 2011 11:31:40 +1100 [thread overview]
Message-ID: <20111212003140.GA16353@thor.bakeyournoodle.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1112120020330.21970@pobox.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Mon, Dec 12, 2011 at 12:21:16AM +0100, Jiri Kosina wrote:
> On Thu, 8 Dec 2011, Jeremy Fitzhardinge wrote:
> >
> > Hm. How about making it "depends on HID && POWER_SUPPLY"? I think that
> > would needlessly disable it if HID is also modular, but I'm not sure how
> > to fix that. "depends on HID && POWER_SUPPLY && HID == POWER_SUPPLY"?
That would work, but I think technically I think you could end up with
HID=m and POWER_SUPPLY=m which would still allow HID_BATTERY_STRENGTH=y
which is the same problem.
I don't know what kind of .config contortions you'd need to do to get
there.
> How about making it 'default POWER_SUPPLY' instead?
By itself that wont help as POWER_SUPPLY=m statisfies.
So it looks like we have Jeremy's:
HID && POWER_SUPPLY && HID == POWER_SUPPLY
or my:
POWER_SUPPLY=y
Yours Tony
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-12 0:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 1:27 linux-next bad Kconfig for drivers/hid Tony Breeds
2011-12-09 5:33 ` Jeremy Fitzhardinge
2011-12-09 19:00 ` Randy Dunlap
2011-12-11 23:21 ` Jiri Kosina
2011-12-12 0:31 ` Tony Breeds [this message]
2011-12-15 10:08 ` Jiri Kosina
2011-12-15 11:44 ` Tony Breeds
2011-12-15 17:43 ` 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=20111212003140.GA16353@thor.bakeyournoodle.com \
--to=tony@bakeyournoodle$(echo .)com \
--cc=jeremy@goop$(echo .)org \
--cc=jkosina@suse$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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