From: Jonathan Cameron <jic23@kernel.org>
To: inv.git-commit@tdk.com
Cc: robh@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, lars@metafoo.de, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org,
Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Subject: Re: [PATCH v3 0/2] iio: imu: inv_icm42600: add support of ICM-42688-P
Date: Sat, 13 Apr 2024 12:07:48 +0100 [thread overview]
Message-ID: <20240413120748.678d6154@jic23-huawei> (raw)
In-Reply-To: <20240408090720.847107-1-inv.git-commit@tdk.com>
On Mon, 8 Apr 2024 09:07:18 +0000
inv.git-commit@tdk.com wrote:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
>
> This series is for adding support of high-end specs ICM-42688-P chip.
Applied.
Thanks,
>
> Changelog:
> * v2: change order of chip definitions and order of patches
> * v3: add patch description and resend without email IP header issue
>
> Jean-Baptiste Maneyrol (2):
> dt-bindings: iio: imu: add icm42688 inside inv_icm42600
> iio: imu: inv_icm42600: add support of ICM-42688-P
>
> .../devicetree/bindings/iio/imu/invensense,icm42600.yaml | 1 +
> drivers/iio/imu/inv_icm42600/inv_icm42600.h | 2 ++
> drivers/iio/imu/inv_icm42600/inv_icm42600_core.c | 5 +++++
> drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c | 3 +++
> drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c | 3 +++
> 5 files changed, 14 insertions(+)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2024-04-13 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 9:07 [PATCH v3 0/2] iio: imu: inv_icm42600: add support of ICM-42688-P inv.git-commit
2024-04-08 9:07 ` [PATCH v3 1/2] dt-bindings: iio: imu: add icm42688 inside inv_icm42600 inv.git-commit
2024-04-08 9:52 ` Krzysztof Kozlowski
2024-04-08 9:07 ` [PATCH v3 2/2] iio: imu: inv_icm42600: add support of ICM-42688-P inv.git-commit
2024-04-13 11:07 ` 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=20240413120748.678d6154@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inv.git-commit@tdk.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=robh@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).