From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
j.anaszewski@samsung.com, jogo@openwrt.org, cernekee@gmail.com,
f.fainelli@gmail.com
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH 1/4] leds-bcm6328: print invalid LED
Date: Thu, 8 Oct 2015 12:35:52 +0200 [thread overview]
Message-ID: <1444300555-13988-2-git-send-email-noltari@gmail.com> (raw)
In-Reply-To: <1444300555-13988-1-git-send-email-noltari@gmail.com>
Print invalid LED instead of warning only about maximum LED value.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
---
drivers/leds/leds-bcm6328.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/leds/leds-bcm6328.c b/drivers/leds/leds-bcm6328.c
index 986fe1e..5daf7be 100644
--- a/drivers/leds/leds-bcm6328.c
+++ b/drivers/leds/leds-bcm6328.c
@@ -373,7 +373,7 @@ static int bcm6328_leds_probe(struct platform_device *pdev)
continue;
if (reg >= BCM6328_LED_MAX_COUNT) {
- dev_err(dev, "invalid LED (>= %d)\n",
+ dev_err(dev, "invalid LED (%u >= %d)\n", reg,
BCM6328_LED_MAX_COUNT);
continue;
}
--
1.9.1
next prev parent reply other threads:[~2015-10-08 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 10:35 [PATCH 0/4] leds-bcm6328: several fixes and improvements Álvaro Fernández Rojas
2015-10-08 10:35 ` Álvaro Fernández Rojas [this message]
2015-10-08 10:35 ` [PATCH 2/4] leds-bcm6328: simplify and improve default-state handling Álvaro Fernández Rojas
[not found] ` <1444300555-13988-1-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-08 10:35 ` [PATCH 3/4] leds-bcm6328: add more init configuration options Álvaro Fernández Rojas
2015-10-08 10:35 ` [PATCH 4/4] Documentation: leds: update DT bindings for leds-bcm6328 Álvaro Fernández Rojas
2015-10-09 10:20 ` [PATCH 0/4] leds-bcm6328: several fixes and improvements Jacek Anaszewski
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=1444300555-13988-2-git-send-email-noltari@gmail.com \
--to=noltari@gmail.com \
--cc=cernekee@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=jogo@openwrt.org \
--cc=linux-leds@vger.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;
as well as URLs for NNTP newsgroup(s).