From: Richard Purdie <rpurdie@rpsys.net>
To: Daniel Mack <daniel@caiaq.de>
Cc: Arnd Hannemann <hannemann@nets.rwth-aachen.de>,
Arnd Hannemann <Arnd.Hannemann@nets.rwth-aachen.de>,
LKML <linux-kernel@vger.kernel.org>,
"linux-geode@lists.infradead.org"
<linux-geode@lists.infradead.org>
Subject: Re: 2.6.33-rc3 regression: leds_alix2: can't allocate I/O for GPIO
Date: Mon, 18 Jan 2010 13:59:35 +0000 [thread overview]
Message-ID: <1263823175.26227.102.camel@dax.rpnet.com> (raw)
In-Reply-To: <20100110122754.GC8970@buzzloop.caiaq.de>
On Sun, 2010-01-10 at 13:27 +0100, Daniel Mack wrote:
> Subject: [PATCH] LEDS: ALIX2: Add dependency to !GPIO_CS5335
>
> The ALIX2 LED driver and the CS5535 GPIO drivers share the same I/O
> range which causes a conflict if they're both enabled. Fix this for now
> by adding Kconfig dependencies. While at it, also drop the EXPERIMENTAL
> flag, as the code has been around for awhile already.
>
> Note that this is a hack. At some point, a real platform support for
> this board should be added which handles the LEDs via the leds-gpio
> driver.
Queued in the LED tree, thanks. I'll push this one to Linus shortly for
2.6.33.
Richard
--
Richard Purdie
Intel Open Source Technology Centre
prev parent reply other threads:[~2010-01-18 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 10:26 2.6.33-rc3 regression: leds_alix2: can't allocate I/O for GPIO Arnd Hannemann
2010-01-07 10:51 ` Richard Purdie
2010-01-07 11:58 ` Arnd Hannemann
2010-01-07 12:11 ` Arnd Hannemann
2010-01-07 12:46 ` Daniel Mack
2010-01-07 14:00 ` Arnd Hannemann
2010-01-07 14:20 ` Daniel Mack
2010-01-07 17:27 ` Richard Purdie
2010-01-08 3:08 ` Daniel Mack
2010-01-08 8:32 ` Arnd Hannemann
2010-01-10 12:27 ` Daniel Mack
2010-01-16 18:52 ` Daniel Mack
2010-01-18 13:59 ` Richard Purdie [this message]
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=1263823175.26227.102.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=Arnd.Hannemann@nets.rwth-aachen.de \
--cc=daniel@caiaq.de \
--cc=hannemann@nets.rwth-aachen.de \
--cc=linux-geode@lists.infradead.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).