From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>
Cc: Brian Norris <briannorris@chromium.org>,
Andy Shevchenko <andy@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Subject: [PATCH v3 0/2] iio: fxas210002c: Discard pm_runtime_put_autosuspend() return and related cleanup.
Date: Mon, 26 Oct 2026 03:20:49 +0000 [thread overview]
Message-ID: <20261026032051.1004536-1-jic23@kernel.org> (raw)
From: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
This is broken out from
https://lore.kernel.org/linux-iio/20261021235818.3059519-1-briannorris@chromium.org/
[PATCH v2 00/17] iio: Stop looking at pm_runtime_put_autosuspend() return codes
Understandably Brian has expressed that his series was focused on
just one thing - dropping the return values. Given this highlighted
some other related code improvements, I am going to have little series
expanding on individual patches from Brian's series - tweaking Brian's
patches where I think it makes sense and adding additional patches
for related cleanup.
Note, if I run out of time and we are near the end of the cycle I
may just pick up Brian's more minimal set!
Brian Norris (1):
iio: gyro: fxas21002c: Discard pm_runtime_put_autosuspend() return
values
Jonathan Cameron (1):
iio: gyro: fxs210002c: Use guard(mutex)() for remaining simple cases.
drivers/iio/gyro/fxas21002c_core.c | 137 +++++++++--------------------
1 file changed, 44 insertions(+), 93 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-26 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 3:20 Jonathan Cameron [this message]
2026-10-26 3:20 ` [PATCH v3 1/2] iio: gyro: fxas21002c: Discard pm_runtime_put_autosuspend() return values Jonathan Cameron
2026-10-26 9:54 ` Andy Shevchenko
2026-10-26 17:42 ` Brian Norris
2026-10-26 3:20 ` [PATCH v3 2/2] iio: gyro: fxs210002c: Use guard(mutex)() for remaining simple cases Jonathan Cameron
2026-10-26 9:56 ` Andy Shevchenko
2026-10-26 17:48 ` Brian Norris
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=20261026032051.1004536-1-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=briannorris@chromium.org \
--cc=dlechner@baylibre.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=linux-iio@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