Linux IIO development
 help / color / mirror / Atom feed
From: "Maxwell Doose" <m32285159@gmail.com>
To: "Angus Gardner" <angusg778@gmail.com>, <linux-iio@vger.kernel.org>
Cc: <linux-staging@lists.linux.dev>, <gregkh@linuxfoundation.org>,
	<jic23@kernel.org>, <lars@metafoo.de>,
	<Michael.Hennerich@analog.com>
Subject: Re: [PATCH] staging: iio: ad9834: fix probe error handling and comment typo
Date: Sat, 02 May 2026 14:54:17 -0500	[thread overview]
Message-ID: <DI8GD8RZU94B.Q3VZJO6EIP3N@gmail.com> (raw)
In-Reply-To: <20260502021815.3953423-1-angusg778@gmail.com>

Hi Angus,

On Fri May 1, 2026 at 9:18 PM CDT, Angus Gardner <angusg778@gmail.com> wrote:
> Use dev_err_probe() for the master clock error path instead of open-coding
> dev_err() + PTR_ERR(), consistent with the avdd regulator error path above
> it and with the equivalent driver ad9832.c.
>
> Simplify the -ENOMEM return after devm_iio_device_alloc() to a direct
> return rather than bouncing through a local variable.
>
> Fix a copy-paste typo in two comments that referred to 'AD9843' instead
> of the correct chip name 'AD9834'.
>
> Signed-off-by: Angus Gardner <angusg778@gmail.com>
> ---
>  drivers/staging/iio/frequency/ad9834.c | 17 +++++++----------
>  1 file changed, 7 insertions(+), 10 deletions(-)
>

Patch itself looks good but maybe rephrase subject to say "Use probe
error handling and fix comment typo" instead? "Fix" seems a bit generic
for my tastes, and we're not really fixing anything anyways.

I'm not the final authority on naming so its at the discretion of
either Andy or Jonathan, and maybe Greg. So either way,
Reviewed-by: Maxwell Doose <m32285159@gmail.com>

best regards,
maxwell

  reply	other threads:[~2026-05-02 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-02  2:18 [PATCH] staging: iio: ad9834: fix probe error handling and comment typo Angus Gardner
2026-05-02 19:54 ` Maxwell Doose [this message]
2026-05-03  8:53   ` Joshua Crofts
2026-05-03 15:07     ` Maxwell Doose

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=DI8GD8RZU94B.Q3VZJO6EIP3N@gmail.com \
    --to=m32285159@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=angusg778@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.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