From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: sre@kernel.org, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, agross@kernel.org,
andersson@kernel.org, konrad.dybcio@linaro.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
Ruan Jinjie <ruanjinjie@huawei.com>
Subject: Re: [PATCH -next v2] power: supply: Remove redundant dev_err_probe() for platform_get_irq_byname()
Date: Tue, 12 Sep 2023 21:08:13 +0200 [thread overview]
Message-ID: <169454569333.510054.8343708350305953046.b4-ty@collabora.com> (raw)
In-Reply-To: <20230727113550.2599335-1-ruanjinjie@huawei.com>
On Thu, 27 Jul 2023 19:35:50 +0800, Ruan Jinjie wrote:
> There is no need to call the dev_err_probe() function directly to print
> a custom message when handling an error from platform_get_irq_byname()
> function as it is going to display an appropriate error message
> in case of a failure.
>
>
Applied, thanks!
[1/1] power: supply: Remove redundant dev_err_probe() for platform_get_irq_byname()
commit: 389405146ca11d24f85b3277121a58f98a926a28
Best regards,
--
Sebastian Reichel <sebastian.reichel@collabora.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-09-12 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 11:35 [PATCH -next v2] power: supply: Remove redundant dev_err_probe() for platform_get_irq_byname() Ruan Jinjie
2023-07-28 8:14 ` Dhruva Gole
2023-09-12 19:08 ` Sebastian Reichel [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=169454569333.510054.8343708350305953046.b4-ty@collabora.com \
--to=sebastian.reichel@collabora.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=ruanjinjie@huawei.com \
--cc=sre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox