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>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] BMI270 data ready interrupt support
Date: Sun, 2 Mar 2025 11:29:25 +0000	[thread overview]
Message-ID: <20250302112925.05d3e593@jic23-huawei> (raw)
In-Reply-To: <20250228-bmi270-irq-v2-0-3f97a4e8f551@gmail.com>

On Fri, 28 Feb 2025 20:03:47 -0300
Gustavo Silva <gustavograzs@gmail.com> wrote:

> This series adds support for data ready interrupt to the BMI270 driver
> using one of the available interrupt pins.
> 
> Additionally, this series includes some cleanups to simplify and improve
> consistency across the driver.
> 
> Signed-off-by: Gustavo Silva <gustavograzs@gmail.com>
I'd already picked up patch 1 from v1, so applied 2 and 3 from this.

Applied to the togreg branch of iio.git but I'll push out briefly as
testing to let 0-day take an initial look.

Thanks,

Jonathan

> ---
> Changes in v2:
> - Patch 2: Updated the commit message to clarify that the variable
>   'bmi270_data::data' has also been renamed.
> - Patch 2: Fixed some line wraps after renaming variables.
> - Link to v1: https://lore.kernel.org/r/20250219-bmi270-irq-v1-0-145d02bbca3b@gmail.com
> 
> ---
> Gustavo Silva (3):
>       iio: imu: bmi270: move private struct declaration to source file
>       iio: imu: bmi270: rename variable bmi270_device to data
>       iio: imu: bmi270: add support for data ready interrupt trigger
> 
>  drivers/iio/imu/bmi270/bmi270.h      |  17 +-
>  drivers/iio/imu/bmi270/bmi270_core.c | 332 +++++++++++++++++++++++++++++------
>  2 files changed, 283 insertions(+), 66 deletions(-)
> ---
> base-commit: c0f115a8d97599623294c8e9ec28530e19c1e85b
> change-id: 20250219-bmi270-irq-9a2bc41faee3
> 
> Best regards,


      parent reply	other threads:[~2025-03-02 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 23:03 [PATCH v2 0/3] BMI270 data ready interrupt support Gustavo Silva
2025-02-28 23:03 ` [PATCH v2 1/3] iio: imu: bmi270: move private struct declaration to source file Gustavo Silva
2025-02-28 23:03 ` [PATCH v2 2/3] iio: imu: bmi270: rename variable bmi270_device to data Gustavo Silva
2025-02-28 23:03 ` [PATCH v2 3/3] iio: imu: bmi270: add support for data ready interrupt trigger Gustavo Silva
2025-03-02 11:29 ` Jonathan Cameron [this message]

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=20250302112925.05d3e593@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=gustavograzs@gmail.com \
    --cc=lanzano.alex@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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