public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: robh@kernel.org, alexandre.belloni@bootlin.com, lars@metafoo.de,
	heiko@sntech.de, linux-iio@vger.kernel.org,
	claudiu.beznea@tuxon.dev, yangyingliang@huawei.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next v3 0/3] iio: adc: at91_adc: Cleanup with the helpers
Date: Mon, 28 Aug 2023 12:12:22 +0100	[thread overview]
Message-ID: <20230828121222.114c728a@jic23-huawei> (raw)
In-Reply-To: <20230828064546.2383857-1-ruanjinjie@huawei.com>

On Mon, 28 Aug 2023 14:45:43 +0800
Jinjie Ruan <ruanjinjie@huawei.com> wrote:

> Commit 7ef9651e9792 ("clk: Provide new devm_clk helpers for prepared
> and enabled clocks") provides a new helper function to prepare and
> enable a clock which keeps prepared (or enabled) during the whole
> lifetime of the driver.
> 
> Use devm_request_irq() to request the interrupt, so we can
> avoid having to manually clean this up.
> 
> Use the dev_err_probe() helper to simplify error handling during probe.
> This also handle scenario, when EDEFER is returned and useless
> error is printed.
> 
> changes in v3:
> - Take the last remove free_irq() and add it to be the first devm managed.
> - Not going any longer than 80 chars than is necessary.
> 
> Changes in v2:
> - Also use devm_request_irq() and dev_err_probe() to clean up the at91_adc.
> - Split the at91_adc patch out to be a new patch set.
> 
> Jinjie Ruan (3):
>   iio: adc: at91_adc: Use devm_request_irq() helper function
>   iio: adc: at91_adc: Use devm_clk_get_enabled() helper function
>   iio: adc: at91_adc: Simplify with dev_err_probe()
> 
>  drivers/iio/adc/at91_adc.c | 108 +++++++++++++------------------------
>  1 file changed, 37 insertions(+), 71 deletions(-)
> 

Series applied.

Thanks for jumping through the various hoops that came up in review!

Note that whilst I have applied this, that is mostly about my tracking
rather than meaning others cannot continue to comment on it.

I won't be pushing this out as a non rebasing tree (which linux-next will
pick up) for a few weeks.

Jonathan

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2023-08-28 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28  6:45 [PATCH -next v3 0/3] iio: adc: at91_adc: Cleanup with the helpers Jinjie Ruan
2023-08-28  6:45 ` [PATCH -next v3 1/3] iio: adc: at91_adc: Use devm_request_irq() helper function Jinjie Ruan
2023-08-28  6:45 ` [PATCH -next v3 2/3] iio: adc: at91_adc: Use devm_clk_get_enabled() " Jinjie Ruan
2023-08-28  6:45 ` [PATCH -next v3 3/3] iio: adc: at91_adc: Simplify with dev_err_probe() Jinjie Ruan
2023-08-28 11:12 ` Jonathan Cameron [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=20230828121222.114c728a@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=heiko@sntech.de \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=ruanjinjie@huawei.com \
    --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