mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Ricardo Ribalda Delgado <ribalda@kernel.org>,
	Dan Murphy <dmurphy@ti.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: core: Fix warning message when init_data
Date: Mon, 6 Apr 2020 23:13:07 +0200	[thread overview]
Message-ID: <20200406211307.GD12611@amd.ucw.cz> (raw)
In-Reply-To: <ef851b8f-0232-ab09-482e-ae575fb8dbde@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]

On Wed 2020-04-01 21:49:00, Jacek Anaszewski wrote:
> Hi Ricardo,
> 
> Thank you for the patch.
> 
> On 4/1/20 11:51 AM, Ricardo Ribalda Delgado wrote:
> > The warning message when a led is renamed due to name collition can fail
> > to show proper original name if init_data is used. Eg:
> > 
> > [    9.073996] leds-gpio a0040000.leds_0: Led (null) renamed to red_led_1 due to name collision
> > 
> > Fixes: bb4e9af0348d ("leds: core: Add support for composing LED class device names")
> > Signed-off-by: Ricardo Ribalda Delgado <ribalda@kernel.org>
> > ---
> >  drivers/leds/led-class.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
> > index 1fc40e8af75e..3363a6551a70 100644
> > --- a/drivers/leds/led-class.c
> > +++ b/drivers/leds/led-class.c
> > @@ -376,7 +376,7 @@ int led_classdev_register_ext(struct device *parent,
> >  
> >  	if (ret)
> >  		dev_warn(parent, "Led %s renamed to %s due to name collision",
> > -				led_cdev->name, dev_name(led_cdev->dev));
> > +				proposed_name, dev_name(led_cdev->dev));
> >  
> >  	if (led_cdev->flags & LED_BRIGHT_HW_CHANGED) {
> >  		ret = led_add_brightness_hw_changed(led_cdev);
> > 
> 
> Acked-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>

Thanks, applied.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2020-04-06 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01  9:51 Ricardo Ribalda Delgado
2020-04-01 19:49 ` Jacek Anaszewski
2020-04-06 21:13   ` Pavel Machek [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=20200406211307.GD12611@amd.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=ribalda@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

Powered by JetHome