Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Alexandru Ardelean <aardelean@deviqon.com>,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: adc: rn5t618-adc: use devm_iio_map_array_register() function
Date: Thu, 30 Sep 2021 17:15:35 +0100	[thread overview]
Message-ID: <20210930171535.5ede99c7@jic23-huawei> (raw)
In-Reply-To: <20210927220834.014e6c77@aktux>

On Mon, 27 Sep 2021 22:08:34 +0200
Andreas Kemnade <andreas@kemnade.info> wrote:

> On Sun, 26 Sep 2021 19:28:59 +0300
> Alexandru Ardelean <aardelean@deviqon.com> wrote:
> 
> > This driver already hooks a similar unwind callback via
> > devm_add_action_or_reset().
> > 
> > They pretty much do the same thing, so this change converts it to the
> > devm_iio_map_array_register().
> > 
> > Signed-off-by: Alexandru Ardelean <aardelean@deviqon.com>
> > ---
> >  drivers/iio/adc/rn5t618-adc.c | 13 +------------
> >  1 file changed, 1 insertion(+), 12 deletions(-)  
> 
> yes, looks sane, the patches it depens on are not in linux-next yet.
I was waiting for 0-day confirmation which for some reason has gone astray
(not problems reported either).  Ah well - I'll assume it's fine and
risk next breakage.

> But it seems that they are accepted, so:
> 
> Reviewed-by: Andreas Kemnade <andreas@kemnade.info>
Thanks and applied to the togreg branch of iio.git, pushed out as testing to
see if 0-day notices this time.

Thanks,

Jonathan


      reply	other threads:[~2021-09-30 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26 16:28 [PATCH] iio: adc: rn5t618-adc: use devm_iio_map_array_register() function Alexandru Ardelean
2021-09-27 20:08 ` Andreas Kemnade
2021-09-30 16:15   ` 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=20210930171535.5ede99c7@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=aardelean@deviqon.com \
    --cc=andreas@kemnade.info \
    --cc=linux-iio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox