From: Daniel Thompson <daniel.thompson@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Lee Jones <lee@kernel.org>, Jingoo Han <jingoohan1@gmail.com>,
Helge Deller <deller@gmx.de>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/7] backlight: gpio: Simplify with dev_err_probe()
Date: Tue, 5 Mar 2024 09:05:36 +0000 [thread overview]
Message-ID: <20240305090536.GJ102563@aspen.lan> (raw)
In-Reply-To: <20240305-backlight-probe-v2-1-609b0cf24bde@linaro.org>
On Tue, Mar 05, 2024 at 09:11:56AM +0100, Krzysztof Kozlowski wrote:
> Common pattern of handling deferred probe can be simplified with
> dev_err_probe(). Less code and also it prints the error value.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>
Daniel.
next prev parent reply other threads:[~2024-03-05 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 8:11 [PATCH v2 0/7] backlight: Simplify probe in few drivers Krzysztof Kozlowski
2024-03-05 8:11 ` [PATCH v2 1/7] backlight: gpio: Simplify with dev_err_probe() Krzysztof Kozlowski
2024-03-05 9:05 ` Daniel Thompson [this message]
2024-03-05 8:11 ` [PATCH v2 2/7] backlight: l4f00242t03: " Krzysztof Kozlowski
2024-03-05 8:11 ` [PATCH v2 3/7] backlight: bd6107: Handle deferred probe Krzysztof Kozlowski
2024-03-05 8:11 ` [PATCH v2 4/7] backlight: as3711_bl: " Krzysztof Kozlowski
2024-03-05 8:12 ` [PATCH v2 5/7] backlight: lm3630a_bl: " Krzysztof Kozlowski
2024-03-05 8:12 ` [PATCH v2 6/7] backlight: lm3630a_bl: Simplify probe return on gpio request error Krzysztof Kozlowski
2024-03-05 8:12 ` [PATCH v2 7/7] backlight: pandora_bl: Drop unneeded ENOMEM error message Krzysztof Kozlowski
2024-03-05 10:04 ` [PATCH v2 0/7] backlight: Simplify probe in few drivers Lee Jones
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=20240305090536.GJ102563@aspen.lan \
--to=daniel.thompson@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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 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.