From: "Luca Tettamanti" <kronos.it@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] Fix compile error with wifi & leds
Date: Mon, 28 Apr 2008 10:16:35 +0200 [thread overview]
Message-ID: <68676e00804280116j7b44c2adwdaa488d078cb94a1@mail.gmail.com> (raw)
In-Reply-To: <20080428075452.GB16379@cs181133002.pp.htv.fi>
On Mon, Apr 28, 2008 at 9:54 AM, Adrian Bunk <bunk@kernel.org> wrote:
> On Mon, Apr 28, 2008 at 10:45:31AM +0300, Adrian Bunk wrote:
> > Can you send the .config that gives this problem?
Just select IWL4965_LEDS without enabling LEDS_TRIGGERS.
> Scrap that, I already got the problem (and your patch looks right).
It works, yes - but I don't like it... NEW_LEDS enables the core code
of the leds driver but also enables/disables the compilation of the
whole driver/leds directory; *every* user of the led driver has to
select whatever config option it wants (e.g. LEDS_TRIGGERS) _plus_
NEW_LEDS, otherwise led code won't be compiled.
>From a quick inspection RT2{4,5}00PCI_LEDS
(driver/net/wireless/rt2x00) have the same problem, they select
LEDS_CLASS without enabling NEW_LEDS -> unresolved symbols :|
Maybe LEDS_* should also select NEW_LEDS?
Luca
next prev parent reply other threads:[~2008-04-28 8:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 20:34 Luca Tettamanti
2008-04-26 23:26 ` Tomas Winkler
2008-04-27 0:40 ` David Miller
2008-04-28 7:45 ` Adrian Bunk
2008-04-28 7:54 ` Adrian Bunk
2008-04-28 8:16 ` Luca Tettamanti [this message]
2008-04-28 8:18 ` Tomas Winkler
2008-04-28 8:20 ` Adrian Bunk
2008-04-28 8:29 ` Tomas Winkler
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=68676e00804280116j7b44c2adwdaa488d078cb94a1@mail.gmail.com \
--to=kronos.it@gmail.com \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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®