From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: linux-leds@vger.kernel.org, colin.king@canonical.com,
dan.carpenter@oracle.com, ncase@xes-inc.com
Subject: Re: [PATCH] leds: pca955x: Prevent crippled LED device name
Date: Mon, 28 Aug 2017 12:12:30 +0200 [thread overview]
Message-ID: <20170828101229.GB18012@amd> (raw)
In-Reply-To: <1503003364-14952-1-git-send-email-jacek.anaszewski@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On Thu 2017-08-17 22:56:04, Jacek Anaszewski wrote:
> In case platform data provided empty LED name string the resulting
> LED class device name would be crippled. Use corresponding LED chip
> bit in place of "function" segment of LED class device name then to
> make the LEDs at least distinguishable.
>
> Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> Reported-by: Colin King <colin.king@canonical.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Suggested-by: Nate Case <ncase@xes-inc.com>
If anyone knows driver that triggers this codepath, please speak
up... we want to fix it, too.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-08-28 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 20:56 [PATCH] leds: pca955x: Prevent crippled LED device name Jacek Anaszewski
2017-08-22 18:46 ` Jacek Anaszewski
2017-08-28 10:12 ` 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=20170828101229.GB18012@amd \
--to=pavel@ucw.cz \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=ncase@xes-inc.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;
as well as URLs for NNTP newsgroup(s).