From: Thierry Reding <thierry.reding@avionic-design.de>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Richard Purdie <rpurdie@linux.intel.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Wim Van Sebroeck <wim@iguana.be>,
linux-kernel@vger.kernel.org
Subject: Re: ARCH_PXA_ADX
Date: Tue, 15 Nov 2011 11:18:17 +0100 [thread overview]
Message-ID: <20111115101817.GA6907@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <1321351777.20271.166.camel@x61.thuisdomein>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
* Paul Bolle wrote:
> 0) Since v2.6.32 the mainline tree supports the "Avionic Design Xanthos
> Backlight Driver" (BACKLIGHT_ADX) and the "Avionic Design Xanthos
> watchdog" driver (ADX_WATCHDOG). These were added in commit 3b96ea9ef8
> ("[...] Add support for the Avionic Design Xanthos backlight device.")
> and 38461c5c08 ("[...] Add support for the Avionic Design Xanthos
> watchdog timer.").
>
> 1) Both drivers' Kconfig symbols depend on the Kconfig symbol
> ARCH_PXA_ADX. At that time this symbol didn't exist. It still doesn't. I
> haven't been able to find anything remotely related (ie, I even did
> things like "git grep -i PXA | grep -i ADX").
>
> 2) So it seems these two drivers could never have been built from the
> mainline tree. (I'm starting to think that the config tools should
> somehow check stuff like this.)
>
> 3) Is the above correct? If it is, why shouldn't I submit the trivial
> patch to remove both these drivers?
Yes, all of that is correct. Unfortunately, I never got around to mainlining
the rest of the code. Feel free to remove both drivers and add my Acked-by.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-11-15 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 10:09 ARCH_PXA_ADX Paul Bolle
2011-11-15 10:18 ` Thierry Reding [this message]
2011-11-15 10:28 ` ARCH_PXA_ADX Wim Van Sebroeck
2011-11-15 10:57 ` ARCH_PXA_ADX Paul Bolle
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=20111115101817.GA6907@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rpurdie@linux.intel.com \
--cc=wim@iguana.be \
/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®