From: Dan Murphy <dmurphy@ti.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: LEDs next branch
Date: Tue, 30 Jul 2019 15:47:15 -0500 [thread overview]
Message-ID: <aa841c27-d3af-01bf-6a90-afeea83e3775@ti.com> (raw)
In-Reply-To: <5be9a3a2-810b-c08a-e631-b7afa005a136@gmail.com>
Jacek
On 7/30/19 3:30 PM, Jacek Anaszewski wrote:
> Hi Dan,
>
> On 7/30/19 8:40 PM, Dan Murphy wrote:
>> Jacek
>>
>> Did you see/fix this on the led-next branch?
>>
>> I saw this when booting trying to fix the lm3532
>>
>> [ 8.651461] led_class: exports duplicate symbol
>> devm_led_classdev_register_ext (owned by kernel)
>>
>> [ 8.730063] led_class: exports duplicate symbol
>> devm_led_classdev_register_ext (owned by kernel)
> I've just tried next-20190730 and haven't noticed anything like that.
> I've checked both with driver compiled-in and loaded as a module.
>
> Tested on qemu versatile board, with tweaked versatile-pb.dts
> to include lm3532 DT node.
>
> There is one issue currently in next but seems to be irrelevant and
> can be fixed with [0].
Thanks for checking I will see if I can track it down.
Dan
> [0] https://lkml.org/lkml/2019/7/22/720
>
next prev parent reply other threads:[~2019-07-30 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 18:40 LEDs next branch Dan Murphy
2019-07-30 20:30 ` Jacek Anaszewski
2019-07-30 20:47 ` Dan Murphy [this message]
2019-07-30 21:11 ` Dan Murphy
2019-07-31 12:11 ` Dan Murphy
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=aa841c27-d3af-01bf-6a90-afeea83e3775@ti.com \
--to=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).