From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Jonathan Cameron <jonathan.cameron@huawei.com>,
Hsin-Yi Wang <hsinyi@chromium.org>
Cc: Eduardo Valentin <edubezval@gmail.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Zhang Rui <rui.zhang@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] thermal-generic-adc: Silent error message for EPROBE_DEFER
Date: Tue, 8 Oct 2019 15:57:37 +0200 [thread overview]
Message-ID: <936ab76a-e2cc-88df-f84f-90aa29d01ae7@linaro.org> (raw)
In-Reply-To: <20191008124520.000009c7@huawei.com>
On 08/10/2019 13:45, Jonathan Cameron wrote:
> On Mon, 7 Oct 2019 10:07:22 -0700
> Hsin-Yi Wang <hsinyi@chromium.org> wrote:
>
>> On Tue, Sep 10, 2019 at 12:59 AM Hsin-Yi Wang <hsinyi@chromium.org> wrote:
>>>
>>> If devm_iio_channel_get() or devm_thermal_zone_of_sensor_register()
>>> fail with EPROBE_DEFER, we shouldn't print an error message, as the
>>> device will be probed again later.
>>>
>>> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
>>> ---
>>
>> Ping on the thread. Any suggestion for this patch?
>> Thanks
>
> Looks sensible to me.
>
> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
I've applied this patch on the testing branch.
Thanks!
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2019-10-08 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 7:59 [PATCH] thermal-generic-adc: Silent error message for EPROBE_DEFER Hsin-Yi Wang
2019-10-07 17:07 ` Hsin-Yi Wang
2019-10-08 11:45 ` Jonathan Cameron
2019-10-08 13:57 ` Daniel Lezcano [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=936ab76a-e2cc-88df-f84f-90aa29d01ae7@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=hsinyi@chromium.org \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.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).