From: Ruan Jinjie <ruanjinjie@huawei.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: robh@kernel.org, alexandre.belloni@bootlin.com, lars@metafoo.de,
heiko@sntech.de, Michael.Hennerich@analog.com,
linux-iio@vger.kernel.org, claudiu.beznea@tuxon.dev,
linux-mediatek@lists.infradead.org, yangyingliang@huawei.com,
matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org,
angelogioacchino.delregno@collabora.com
Subject: Re: [PATCH -next 1/4] iio: adc: at91_adc: Use devm_clk_get_enabled() helper function
Date: Sat, 26 Aug 2023 10:02:47 +0800 [thread overview]
Message-ID: <2b9c3a6d-8d1d-7815-c4ea-59ff77654e3c@huawei.com> (raw)
In-Reply-To: <20230825135015.481d0aff@jic23-huawei>
On 2023/8/25 20:50, Jonathan Cameron wrote:
> te patch moving to
> devm_request_irq() as then the exit paths will become much simpler and you
> can also move to return dev_err_probe() save a few pointless lines of code
> and give the benefit of debug info for deferred return codes.
Right！I'll cleanup these together in v2.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-26 2:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 10:57 [PATCH -next 0/4] iio: Use devm_clk_get_enabled() helper function Jinjie Ruan
2023-08-25 10:57 ` [PATCH -next 1/4] iio: adc: at91_adc: " Jinjie Ruan
2023-08-25 12:50 ` Jonathan Cameron
2023-08-26 2:02 ` Ruan Jinjie [this message]
2023-08-25 10:57 ` [PATCH -next 2/4] iio: adc: mt6577_auxadc: " Jinjie Ruan
2023-08-25 12:54 ` Jonathan Cameron
2023-08-26 2:37 ` Ruan Jinjie
2023-08-25 10:57 ` [PATCH -next 3/4] iio: adc: spear_adc: " Jinjie Ruan
2023-08-25 12:55 ` Jonathan Cameron
2023-08-25 10:57 ` [PATCH -next 4/4] iio: frequency: adf4350: " Jinjie Ruan
2023-08-25 12:57 ` Jonathan Cameron
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=2b9c3a6d-8d1d-7815-c4ea-59ff77654e3c@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandre.belloni@bootlin.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=heiko@sntech.de \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox