From: Pavel Machek <pavel@ucw.cz>
To: Tian Tao <tiantao6@hisilicon.com>
Cc: linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: trigger: pattern: Switch to using the new API kobj_to_dev()
Date: Sun, 25 Apr 2021 23:38:17 +0200 [thread overview]
Message-ID: <20210425213817.GG10996@amd> (raw)
In-Reply-To: <1616380636-7613-1-git-send-email-tiantao6@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
On Mon 2021-03-22 10:37:16, Tian Tao wrote:
> Switch to using the new API kobj_to_dev() to fix the below warnning:
> ./drivers/leds/trigger/ledtrig-pattern.c:336:60-61: WARNING opportunity
> for kobj_to_dev()
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-04-25 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 2:37 [PATCH] leds: trigger: pattern: Switch to using the new API kobj_to_dev() Tian Tao
2021-04-25 21:38 ` 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=20210425213817.GG10996@amd \
--to=pavel@ucw.cz \
--cc=linux-leds@vger.kernel.org \
--cc=tiantao6@hisilicon.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).