From: Jonathan Cameron <jic23@kernel.org>
To: Darius Berghe <darius.berghe@analog.com>
Cc: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<corbet@lwn.net>, <alexandru.tachici@analog.com>,
<lars@metafoo.de>, <Michael.Hennerich@analog.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] iio: imu: add devices to adis16480 driver
Date: Sat, 9 Nov 2024 11:22:12 +0000 [thread overview]
Message-ID: <20241109112212.437a4a96@jic23-huawei> (raw)
In-Reply-To: <20241108125814.3097213-1-darius.berghe@analog.com>
On Fri, 8 Nov 2024 14:58:11 +0200
Darius Berghe <darius.berghe@analog.com> wrote:
> Changes in v3:
> - resend v2 using get_maintainers.pl script, hopefully everyone is in
> the email list now
> - edited the dt-bindings patch to use oneOf
>
> Darius Berghe (3):
> iio: imu: adis16480: add devices to adis16480 driver
> iio: imu: adis16480: add devices to adis16480 - docs
> dt-bindings: iio: adis16480: add devices to adis16480
>
> .../bindings/iio/imu/adi,adis16480.yaml | 42 ++++++-----
> Documentation/iio/adis16480.rst | 3 +
> drivers/iio/imu/adis16480.c | 75 +++++++++++++++++++
> 3 files changed, 102 insertions(+), 18 deletions(-)
>
Applied to the testing branch of iio.git
Note that I'll be rebasing this on 6.13-rc1 once available so
it won't be picked up by linux-next until after that (when I'll
push it out as togreg).
In the meantime, 0-day can have a first look at this.
Jonathan
prev parent reply other threads:[~2024-11-09 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 12:58 [PATCH v3 0/3] iio: imu: add devices to adis16480 driver Darius Berghe
2024-11-08 12:58 ` [PATCH v3 1/3] iio: imu: adis16480: " Darius Berghe
2024-11-08 12:58 ` [PATCH v3 2/3] iio: imu: adis16480: add devices to adis16480 - docs Darius Berghe
2024-11-08 12:58 ` [PATCH v3 3/3] dt-bindings: iio: adis16480: add devices to adis16480 Darius Berghe
2024-11-08 17:43 ` Conor Dooley
2024-11-09 11:22 ` 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=20241109112212.437a4a96@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.tachici@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=darius.berghe@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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