From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Hans Ulli Kroll <ulli.kroll@googlemail.com>,
Alan Mizrahi <alan@mizrahi.com.ve>,
Richard Purdie <rpurdie@rpsys.net>, Pavel Machek <pavel@ucw.cz>
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH] leds: fix wrong dmi_match on PC Engines APU LEDs
Date: Sat, 10 Mar 2018 22:13:55 +0100 [thread overview]
Message-ID: <b51f1f41-e06e-25e6-30f8-a2b9f7e8ffb8@gmail.com> (raw)
In-Reply-To: <20180305170910.8905-1-ulli.kroll@googlemail.com>
Hi Hans,
Thank you for the patch.
On 03/05/2018 06:09 PM, Hans Ulli Kroll wrote:
> APU has compared to APU2 no DMI_BOARD_NAME.
> Use DMI_PRODUCT_NAME instead.
Could we have the commit message more expressive?
Is it that now this driver doesn't work for APU board?
> Signed-off-by: Hans Ulli Kroll <ulli.kroll@googlemail.com>
> ---
> drivers/leds/leds-apu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/leds/leds-apu.c b/drivers/leds/leds-apu.c
> index 74820aab9497..5bbf5c31413e 100644
> --- a/drivers/leds/leds-apu.c
> +++ b/drivers/leds/leds-apu.c
> @@ -206,7 +206,7 @@ static int __init apu_led_probe(struct platform_device *pdev)
>
> apu_led->pdev = pdev;
>
> - if (dmi_match(DMI_BOARD_NAME, "APU")) {
> + if (dmi_match(DMI_PRODUCT_NAME, "APU")) {
> apu_led->profile = apu1_led_profile;
> apu_led->platform = APU1_LED_PLATFORM;
> apu_led->num_led_instances = ARRAY_SIZE(apu1_led_profile);
>
If it fails here, then how it is possible that it succeeds
in the apu_led_init() ?
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2018-03-10 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 17:09 Hans Ulli Kroll
2018-03-10 21:13 ` Jacek Anaszewski [this message]
2018-03-18 14:24 ` Hans Ulli Kroll
2018-03-20 19:40 ` 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=b51f1f41-e06e-25e6-30f8-a2b9f7e8ffb8@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=alan@mizrahi.com.ve \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=ulli.kroll@googlemail.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
all inboxes | Powered by JetHome®