The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Stepan Ionichev <sozdayvek@gmail.com>
Cc: shofiqtest@gmail.com, dlechner@baylibre.com, nuno.sa@analog.com,
	andy@kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] iio: adc: ti-ads1298: Add parentheses around macro parameter
Date: Mon, 11 May 2026 17:05:19 +0100	[thread overview]
Message-ID: <20260511170519.4f381ae2@jic23-huawei> (raw)
In-Reply-To: <20260509113809.26224-1-sozdayvek@gmail.com>

On Sat,  9 May 2026 16:38:09 +0500
Stepan Ionichev <sozdayvek@gmail.com> wrote:

> The current call sites all pass plain identifiers (chan_index,
> channel, i), so this is a preventive hardening rather than a bug
> fix, but wrapping macro arguments matches the kernel macro style
> recommended by checkpatch and avoids surprises for future callers
> that pass an expression.
> 
> Reviewed-by: Stepan Ionichev <sozdayvek@gmail.com>
> 
> Stepan

Picked up this patch.

J

  reply	other threads:[~2026-05-11 16:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09 15:19 [PATCH v4 0/3] iio: adc: ti-ads1298: Minor driver cleanups Md Shofiqul Islam
2026-05-09 15:19 ` [PATCH v4 1/3] iio: adc: ti-ads1298: Add parentheses around macro parameter Md Shofiqul Islam
2026-05-09 11:38   ` Stepan Ionichev
2026-05-11 16:05     ` Jonathan Cameron [this message]
2026-05-09 15:19 ` [PATCH v4 2/3] iio: adc: ti-ads1298: Fix incorrect timeout comment Md Shofiqul Islam
2026-05-09 20:27   ` David Lechner
2026-05-10  6:59     ` Andy Shevchenko
2026-05-11  5:20       ` mike.looijmans
2026-05-11 10:14         ` Andy Shevchenko
2026-05-09 15:19 ` [PATCH v4 3/3] iio: adc: ti-ads1298: Remove unnecessary CONFIG2 write during init Md Shofiqul Islam
2026-05-09 20:36   ` David Lechner
2026-05-11 16:06     ` Jonathan Cameron
2026-05-11 17:59       ` mike.looijmans

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=20260511170519.4f381ae2@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=shofiqtest@gmail.com \
    --cc=sozdayvek@gmail.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