All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Maxwell Doose <m32285159@gmail.com>
Cc: Stepan Ionichev <sozdayvek@gmail.com>,
	andy@kernel.org, giorgitchankvetadze1997@gmail.com,
	jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] iio: chemical: scd30: make command lookup table const
Date: Sun, 10 May 2026 12:08:53 +0300	[thread overview]
Message-ID: <agBLJQBOTm2EEVCJ@ashevche-desk.local> (raw)
In-Reply-To: <CAKqfh0GWMu5WGfSigJOAredavrezZgmPVN9+qmMZ2aMoVX_jYw@mail.gmail.com>

On Sun, May 10, 2026 at 03:04:28AM -0500, Maxwell Doose wrote:
> On Sun, May 10, 2026 at 2:59 AM Stepan Ionichev <sozdayvek@gmail.com> wrote:
> > On Sun, 10 May 2026, Maxwell Doose wrote:
> > > I'm curious, are you having AI do your reviews?
> >
> > English is not my native language, so I use AI to help with phrasing
> > and to learn kernel review style. The technical analysis I do myself
> > -- for this patch I checked via grep that scd30_i2c_cmd_lookup_tbl[]
> > is only read (one read site in scd30_i2c_command() via
> > put_unaligned_be16, no writes), which is what supports the const
> > change being correct.
> 
> Thanks for confirming, just wanted to check since some of the phrasing
> in your review did seem very AI-like.
> 
> > Happy to follow whatever disclosure norm the iio community prefers.
> 
> Typically reviews end up being one-liners (e.g., Reviewed-by: name
> <email>) and that ends up being the whole message, sometimes reviewers
> and maintainers will have inline comments. Obviously you don't have to
> follow those norms but that's just what usually ends up happening.

The good review includes reasoning, and Stepan's is a good one, just needed
clarification, because I haven't got if it's a proposal to have a commit
message changed or summary of the review.

> > Stepan

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-05-10  9:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 13:39 [PATCH] iio: chemical: scd30: make command lookup table const Giorgi Tchankvetadze
2026-05-08 15:07 ` Maxwell Doose
2026-05-09 11:16 ` [PATCH 3/3] " Stepan Ionichev
2026-05-10  0:31   ` Stepan Ionichev
2026-05-10  0:42     ` Stepan Ionichev
2026-05-10  1:05       ` Stepan Ionichev
2026-05-10  8:04       ` Maxwell Doose
2026-05-10  9:08         ` Andy Shevchenko [this message]
2026-05-10  7:52     ` Maxwell Doose
2026-05-10  7:21   ` Andy Shevchenko
2026-05-11 11:28 ` [PATCH] " 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=agBLJQBOTm2EEVCJ@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=giorgitchankvetadze1997@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m32285159@gmail.com \
    --cc=nuno.sa@analog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.