From: arno@natisbad.org (Arnaud Ebalard)
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: Tony Lindgren <tony@atomide.com>, Felipe Balbi <felipe.balbi@nokia.com>
Subject: [PATCH] Remove duplicate Kconfig LEDS_LP5521 entry introduced by 67a32ec7
Date: Wed, 24 Jun 2009 10:59:06 +0200 [thread overview]
Message-ID: <871vpaj9d1.fsf@small.ssi.corp> (raw)
Hi,
While playing with kernel configuration for my N810, I noticed a
duplicate config entry for LEDS_LP5521.
AFAICT, it was added by commit 67a32ec7 (leds: introduce lp5521 led
driver) but the entry was already there from 43350bf4 (leds: lp5521:
move to drivers/leds).
Following patch is against current linux-omap tree.
Cheers,
a+
Signed-off-by: Arnaud Ebalard <arno@natisbad.org>
---
drivers/leds/Kconfig | 10 ----------
1 files changed, 0 insertions(+), 10 deletions(-)
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index 788f48c..0493c17 100644
--- a/drivers/leds/Kconfig
+++ b/drivers/leds/Kconfig
@@ -170,16 +170,6 @@ config LEDS_LP5521
This driver can be built as a module by choosing 'M'. The module
will be called leds-lp5521.
-config LEDS_LP5521
- tristate "LED Support for the LP5521 LEDs"
- depends on LEDS_CLASS && I2C
- help
- If you say 'Y' here you get support for the National Semiconductor
- LP5521 LED driver used in n8x0 boards.
-
- This driver can be built as a module by choosing 'M'. The module
- will be called leds-lp5521.
-
config LEDS_CLEVO_MAIL
tristate "Mail LED on Clevo notebook"
depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI
--
1.6.3.1
next reply other threads:[~2009-06-24 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 8:59 Arnaud Ebalard [this message]
2009-06-24 8:59 ` [PATCH] Remove duplicate Kconfig LEDS_LP5521 entry introduced by 67a32ec7 Felipe Balbi
2009-06-24 10:42 ` Arnaud Ebalard
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=871vpaj9d1.fsf@small.ssi.corp \
--to=arno@natisbad.org \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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