Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Gustavo Silva <gustavograzs@gmail.com>
Cc: "Alex Lanzano" <lanzano.alex@gmail.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Lothar Rubusch" <l.rubusch@gmail.com>
Subject: Re: [PATCH v3 2/3] iio: imu: bmi270: add step counter watermark event
Date: Sun, 22 Jun 2025 12:46:30 +0100	[thread overview]
Message-ID: <20250622124630.052fd593@jic23-huawei> (raw)
In-Reply-To: <20250616-bmi270-events-v3-2-16e37588604f@gmail.com>

On Mon, 16 Jun 2025 20:53:10 -0300
Gustavo Silva <gustavograzs@gmail.com> wrote:

> Add support for generating events when the step counter reaches the
> configurable watermark.
> 
> Reviewed-by: Andy Shevchenko <andy@kernel.org>
> Signed-off-by: Gustavo Silva <gustavograzs@gmail.com>
Applied to the togreg branch of iio.git and pushed out as testing for 0-day
to see what we missed.

Thanks,

Jonathan

  reply	other threads:[~2025-06-22 11:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 23:53 [PATCH v3 0/3] BMI270: Add support for step counter and motion events Gustavo Silva
2025-06-16 23:53 ` [PATCH v3 1/3] iio: imu: bmi270: add channel for step counter Gustavo Silva
2025-06-22 11:44   ` Jonathan Cameron
2025-06-22 12:11     ` Lothar Rubusch
2025-06-22 14:33       ` Jonathan Cameron
2025-06-16 23:53 ` [PATCH v3 2/3] iio: imu: bmi270: add step counter watermark event Gustavo Silva
2025-06-22 11:46   ` Jonathan Cameron [this message]
2025-06-16 23:53 ` [PATCH v3 3/3] iio: imu: bmi270: add support for motion events Gustavo Silva
2025-06-17  6:32   ` Andy Shevchenko
2025-06-22 13:42   ` Jonathan Cameron
2025-06-25  0:17     ` Gustavo Silva

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=20250622124630.052fd593@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gustavograzs@gmail.com \
    --cc=l.rubusch@gmail.com \
    --cc=lanzano.alex@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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