From: Pavel Machek <pavel@ucw.cz>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH -next] leds: tlc591xx: fix return value check in tlc591xx_probe()
Date: Mon, 10 May 2021 11:59:10 +0200 [thread overview]
Message-ID: <20210510095910.GB14728@amd> (raw)
In-Reply-To: <20210406131159.2136509-1-yangyingliang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
On Tue 2021-04-06 21:11:59, Yang Yingliang wrote:
> After device_get_match_data(), tlc591xx is not checked, add
> check for it and also check np after dev_of_node.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Thanks, applied.
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2021-05-10 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 13:11 [PATCH -next] leds: tlc591xx: fix return value check in tlc591xx_probe() Yang Yingliang
2021-05-10 9:59 ` 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=20210510095910.GB14728@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=yangyingliang@huawei.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).