From: Jonathan Cameron <jic23@kernel.org>
To: Angus Gardner <angusg778@gmail.com>
Cc: linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
gregkh@linuxfoundation.org, lars@metafoo.de,
Michael.Hennerich@analog.com
Subject: Re: [PATCH v2 0/3] staging: iio: ad9834: driver cleanup
Date: Mon, 4 May 2026 16:23:46 +0100 [thread overview]
Message-ID: <20260504162346.53668925@jic23-huawei> (raw)
In-Reply-To: <20260504092059.1536094-1-angusg778@gmail.com>
On Mon, 4 May 2026 19:20:56 +1000
Angus Gardner <angusg778@gmail.com> wrote:
> v2: Split into a series of three patches as suggested by reviewer feedback.
> Also add a missing dev_err_probe() conversion for the SPI init error
> path pointed out by Joshua.
>
> v1: https://lore.kernel.org/linux-staging/20260502021815.3953423-1-angusg778@gmail.com/
Hi Angus
Series looks good to me (Thanks Maxwell and Joshua for reviewing!)
Applied to the testing branch of iio.git.
>
> Angus Gardner (3):
> staging: iio: ad9834: simplify -ENOMEM return in probe
> staging: iio: ad9834: use dev_err_probe() in probe function
> staging: iio: ad9834: fix chip name typo in comments
>
> drivers/staging/iio/frequency/ad9834.c | 24 ++++++++++--------------
> 1 file changed, 10 insertions(+), 14 deletions(-)
>
next prev parent reply other threads:[~2026-05-04 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 9:20 [PATCH v2 0/3] staging: iio: ad9834: driver cleanup Angus Gardner
2026-05-04 9:20 ` [PATCH 1/3] staging: iio: ad9834: simplify -ENOMEM return in probe Angus Gardner
2026-05-04 12:37 ` Maxwell Doose
2026-05-04 9:20 ` [PATCH 2/3] staging: iio: ad9834: use dev_err_probe() in probe function Angus Gardner
2026-05-04 9:20 ` [PATCH 3/3] staging: iio: ad9834: fix chip name typo in comments Angus Gardner
2026-05-04 12:33 ` Maxwell Doose
2026-05-04 15:23 ` Jonathan Cameron [this message]
2026-05-04 16:10 ` [PATCH v2 0/3] staging: iio: ad9834: driver cleanup Maxwell Doose
2026-05-04 16:54 ` 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=20260504162346.53668925@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=angusg778@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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