From: Maxwell Doose <m32285159@gmail.com>
To: Angus Gardner <angusg778@gmail.com>
Cc: linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
gregkh@linuxfoundation.org, jic23@kernel.org, lars@metafoo.de,
Michael.Hennerich@analog.com
Subject: Re: [PATCH 3/3] staging: iio: ad9834: fix chip name typo in comments
Date: Mon, 4 May 2026 07:33:52 -0500 [thread overview]
Message-ID: <CAKqfh0Gfwnaj+chzWUvujSVrw6wmqJAhSL9O2eYuZ136QbbD7w@mail.gmail.com> (raw)
In-Reply-To: <20260504092059.1536094-4-angusg778@gmail.com>
On Mon, May 4, 2026 at 4:21 AM Angus Gardner <angusg778@gmail.com> wrote:
>
> Two comments incorrectly refer to 'AD9843' instead of 'AD9834'.
> Fix the copy-paste typo.
>
> Signed-off-by: Angus Gardner <angusg778@gmail.com>
> ---
> drivers/staging/iio/frequency/ad9834.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
[snip]
Looks good to me.
Reviewed-by: Maxwell Doose <m32285159@gmail.com>
best regards,
maxwell
next prev parent reply other threads:[~2026-05-04 12:34 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 [this message]
2026-05-04 15:23 ` [PATCH v2 0/3] staging: iio: ad9834: driver cleanup Jonathan Cameron
2026-05-04 16:10 ` 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=CAKqfh0Gfwnaj+chzWUvujSVrw6wmqJAhSL9O2eYuZ136QbbD7w@mail.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