From: Lee Jones <lee@kernel.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Yang Yingliang <yangyingliang@huawei.com>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
jingoohan1@gmail.com
Subject: Re: [PATCH -next v3] backlight: gpio_backlight: Switch to use dev_err_probe() helper
Date: Wed, 28 Sep 2022 10:11:06 +0100 [thread overview]
Message-ID: <YzQPqjinYYAZdcR+@google.com> (raw)
In-Reply-To: <YzLW6zo/7k031jzi@maple.lan>
On Tue, 27 Sep 2022, Daniel Thompson wrote:
> On Tue, Sep 27, 2022 at 11:31:38AM +0800, Yang Yingliang wrote:
> > In the probe path, dev_err() can be replaced with dev_err_probe()
> > which will check if error code is -EPROBE_DEFER and prints the
> > error name. It also sets the defer probe reason which can be
> > checked later through debugfs. It's more simple in error path.
> >
> > Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>
> Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>
The original patch is not in my inbox.
Was I missed from the original mail?
--
Lee Jones [李琼斯]
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee@kernel.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: jingoohan1@gmail.com, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Yang Yingliang <yangyingliang@huawei.com>
Subject: Re: [PATCH -next v3] backlight: gpio_backlight: Switch to use dev_err_probe() helper
Date: Wed, 28 Sep 2022 10:11:06 +0100 [thread overview]
Message-ID: <YzQPqjinYYAZdcR+@google.com> (raw)
In-Reply-To: <YzLW6zo/7k031jzi@maple.lan>
On Tue, 27 Sep 2022, Daniel Thompson wrote:
> On Tue, Sep 27, 2022 at 11:31:38AM +0800, Yang Yingliang wrote:
> > In the probe path, dev_err() can be replaced with dev_err_probe()
> > which will check if error code is -EPROBE_DEFER and prints the
> > error name. It also sets the defer probe reason which can be
> > checked later through debugfs. It's more simple in error path.
> >
> > Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>
> Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>
The original patch is not in my inbox.
Was I missed from the original mail?
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2022-09-28 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 3:31 [PATCH -next v3] backlight: gpio_backlight: Switch to use dev_err_probe() helper Yang Yingliang
2022-09-27 3:31 ` Yang Yingliang
2022-09-27 10:56 ` Daniel Thompson
2022-09-27 10:56 ` Daniel Thompson
2022-09-28 9:11 ` Lee Jones [this message]
2022-09-28 9:11 ` Lee Jones
2022-09-28 9:25 ` Yang Yingliang
2022-09-28 9:25 ` Yang Yingliang
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=YzQPqjinYYAZdcR+@google.com \
--to=lee@kernel.org \
--cc=daniel.thompson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=linux-fbdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.