From: arno@natisbad.org (Arnaud Ebalard)
To: felipe.balbi@nokia.com
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] Remove duplicate Kconfig LEDS_LP5521 entry introduced by 67a32ec7
Date: Wed, 24 Jun 2009 12:42:49 +0200 [thread overview]
Message-ID: <87ab3xj4k6.fsf@small.ssi.corp> (raw)
In-Reply-To: <20090624085914.GA16639@nokia.com> (Felipe Balbi's message of "Wed, 24 Jun 2009 11:59:14 +0300")
Hi Felipe,
Felipe Balbi <felipe.balbi@nokia.com> writes:
> On Wed, Jun 24, 2009 at 10:59:06AM +0200, ext Arnaud Ebalard wrote:
>> 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.
>
> probably automerge issues.
I have no clue on how it happened. After noticing the duplication, I
just did a git annotate to get some info and then took a look at
associated patches.
Cheers,
a+
prev parent reply other threads:[~2009-06-24 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 8:59 [PATCH] Remove duplicate Kconfig LEDS_LP5521 entry introduced by 67a32ec7 Arnaud Ebalard
2009-06-24 8:59 ` Felipe Balbi
2009-06-24 10:42 ` Arnaud Ebalard [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=87ab3xj4k6.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