From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v1 0/2] iio: imu: st_lsm6dsx: Clean up ACPI/fwnode code paths
Date: Sat, 31 Aug 2024 11:53:43 +0100 [thread overview]
Message-ID: <20240831115343.775c6167@jic23-huawei> (raw)
In-Reply-To: <20240826212344.866928-1-andy.shevchenko@gmail.com>
On Tue, 27 Aug 2024 00:22:38 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> Here is a couple of cleanups that should not affect any functionality.
>
> Andy Shevchenko (2):
> iio: imu: st_lsm6dsx: Use iio_read_acpi_mount_matrix() helper
> iio: imu: st_lsm6dsx: Remove useless dev_fwnode() calls
>
> drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 93 ++------------------
> 1 file changed, 7 insertions(+), 86 deletions(-)
>
Applied the obvious fix for the bot error messages &drdy_pin
and applied to the togreg branch of iio.git (pushed out as testing)
Still time for other reviews however as I'll be rebasing that tree
anyway if Greg takes the pull request I sent last week.
There are some series waiting for fixes to loop back around, hence
this dance.
Jonathan
next prev parent reply other threads:[~2024-08-31 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 21:22 [PATCH v1 0/2] iio: imu: st_lsm6dsx: Clean up ACPI/fwnode code paths Andy Shevchenko
2024-08-26 21:22 ` [PATCH v1 1/2] iio: imu: st_lsm6dsx: Use iio_read_acpi_mount_matrix() helper Andy Shevchenko
2024-08-26 21:22 ` [PATCH v1 2/2] iio: imu: st_lsm6dsx: Remove useless dev_fwnode() calls Andy Shevchenko
2024-08-27 15:01 ` kernel test robot
2024-08-27 15:22 ` kernel test robot
2024-08-27 15:53 ` kernel test robot
2024-08-28 4:52 ` kernel test robot
2024-08-31 10:53 ` Jonathan Cameron [this message]
2024-08-31 11:40 ` [PATCH v1 0/2] iio: imu: st_lsm6dsx: Clean up ACPI/fwnode code paths Andy Shevchenko
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=20240831115343.775c6167@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.