Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Wenqiang Zhao via B4 Relay <devnull+berringtoni36.gmail.com@kernel.org>
Cc: berringtoni36@gmail.com, "Nuno Sá" <nuno.sa@analog.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@intel.com>,
	linux@analog.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Lothar Rubusch" <l.rubusch@gmail.com>,
	"Joshua Crofts" <joshua.crofts1@gmail.com>
Subject: Re: [PATCH v4] iio: accel: adxl345: separate event state from query errors
Date: Sat, 24 Oct 2026 03:49:31 +0100	[thread overview]
Message-ID: <20261024034931.5d954108@jic23-hlaptop> (raw)
In-Reply-To: <20261019-adxl345-event-v4-1@gmail.com>

On Mon, 19 Oct 2026 21:05:20 +0800
Wenqiang Zhao via B4 Relay <devnull+berringtoni36.gmail.com@kernel.org> wrote:

> From: Wenqiang Zhao <berringtoni36@gmail.com>
> 
> The activity/inactivity query helpers return either a boolean result or a
> negative regmap error. adxl345_read_mag_config() converts the latter to 1
> with !!, reporting a failed read as an enabled event. The disable path
> also turns a coupling query error into a successful write.
> 
> Return query status separately from the boolean result by passing bool
> output parameters to both helpers. Rename them from is_* to get_* and
> update the event read, disable and link-bit callers to check the status
> before using the result. Preserve the successful coupling-mismatch
> no-op when disabling an event.
> 
> Fixes: 66a1af6d8a63 ("iio: accel: adxl345: add activity event feature")
> Fixes: 31f7679bb69a ("iio: accel: adxl345: add coupling detection for activity/inactivity")
> Assisted-by: LLM
> Signed-off-by: Wenqiang Zhao <berringtoni36@gmail.com>
For future patches, please don't reply to an existing thread with a new version.
It can cause trouble for tooling and generally makes them harder to spot.
New email thread for each version.

This seems fine to me, so applied. I'm not rushing this one in though
as it doesn't feel very urgent so applied to the testing branch of iio.git.

Thanks,

Jonathan


  reply	other threads:[~2026-10-24  2:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 13:42 [PATCH v3] iio: accel: adxl345: separate event state from query errors Wenqiang Zhao via B4 Relay
2026-10-19 10:20 ` Andy Shevchenko
2026-10-19 12:53   ` Iron Berrington
2026-10-19 13:05 ` [PATCH v4] " Wenqiang Zhao via B4 Relay
2026-10-24  2:49   ` Jonathan Cameron [this message]
2026-10-25  5:52     ` berringtoni36

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=20261024034931.5d954108@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=berringtoni36@gmail.com \
    --cc=devnull+berringtoni36.gmail.com@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=joshua.crofts1@gmail.com \
    --cc=l.rubusch@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@analog.com \
    --cc=nuno.sa@analog.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