From: Ivo van Doorn <ivdoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: rt2400-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Rt2400-devel] next-20080611 rt2x00: build failure
Date: Wed, 11 Jun 2008 20:21:42 +0200 [thread overview]
Message-ID: <200806112021.43707.IvDoorn@gmail.com> (raw)
In-Reply-To: <32664704.1213206386295.JavaMail.oracle-s5rVz5nKm9nKpDp+h9PlwkEOCMrvLtNR@public.gmane.org>
On Wednesday 11 June 2008, Randy Dunlap wrote:
> --- Original Message ---
> > > when CONFIG_INPUT=n and
> > > # CONFIG_NEW_LEDS is not set
> > > CONFIG_LEDS_CLASS=y
> >
> > Does below patch help?
>
> Nope, sorry, same build errors.
Ok this is odd, there is something very strange happening,
the relevant options in your config are:
CONFIG_RFKILL=y
CONFIG_RFKILL_INPUT=y
# CONFIG_INPUT is not set
CONFIG_INPUT_POLLDEV=y
CONFIG_RT2X00_LIB_RFKILL=y
>From net/rfkill/Kconfig:
config RFKILL_INPUT
tristate "Input layer to RF switch connector"
depends on RFKILL && INPUT
So RFKILL_INPUT shouldn't not be enabled because it has
a clear dependency on the CONFIG_INPUT option.
>From drivers/net/wireless/rt2x00/Kconfig
config RT2X00_LIB_RFKILL
boolean
depends on RT2X00_LIB
select RFKILL
select INPUT_POLLDEV
This doesn't mean that the rt2x00 behavior of selecting
CONFIG_INPUT_POLLDEV without dependencies on
CONFIG_INPUT was correct. But more that there is
a secondary bug elsewhere as well, and that is the one
which is causing the build failure now.. :S
Anybody with additional ideas? :)
Ivo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-11 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 17:07 next-20080611 rt2x00: build failure Randy Dunlap
2008-06-11 17:48 ` [Rt2400-devel] " Ivo van Doorn
2008-06-11 17:46 ` Randy Dunlap
[not found] ` <32664704.1213206386295.JavaMail.oracle-s5rVz5nKm9nKpDp+h9PlwkEOCMrvLtNR@public.gmane.org>
2008-06-11 18:21 ` Ivo van Doorn [this message]
[not found] ` <20080611100748.d35829f4.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2008-06-11 18:10 ` John W. Linville
2008-06-11 19:03 ` [Rt2400-devel] " Ivo van Doorn
2008-06-11 19:32 ` Randy Dunlap
[not found] ` <20080611123245.4089f47b.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2008-06-11 19:59 ` Ivo van Doorn
[not found] ` <200806112159.00779.IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-06-11 19:57 ` [PATCH] " Randy Dunlap
2008-06-11 20:32 ` [PATCH] next-20080611 rt2x00: LEDS " Randy Dunlap
2008-06-11 22:15 ` Ivo van Doorn
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=200806112021.43707.IvDoorn@gmail.com \
--to=ivdoorn-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=rt2400-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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;
as well as URLs for NNTP newsgroup(s).