From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Lorenzo Bianconi <lorenzo@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/3] iio: Fix wakeup source leaks on device unbind
Date: Sat, 12 Apr 2025 12:24:54 +0100 [thread overview]
Message-ID: <20250412122454.2a34182b@jic23-huawei> (raw)
In-Reply-To: <20250406-b4-device-wakeup-leak-iio-v1-0-2d7d322a4a93@linaro.org>
On Sun, 06 Apr 2025 22:01:41 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> Device can be unbound, so driver must also release memory for the wakeup
> source.
Applied to the fixes-togreg branch of iio.git.
I haven't marked them for stable as seems the resource leak is fairly
harmless.
Jonathan
>
> Best regards,
> Krzysztof
>
> ---
> Krzysztof Kozlowski (3):
> iio: accel: fxls8962af: Fix wakeup source leaks on device unbind
> iio: adc: qcom-spmi-iadc: Fix wakeup source leaks on device unbind
> iio: imu: st_lsm6dsx: Fix wakeup source leaks on device unbind
>
> drivers/iio/accel/fxls8962af-core.c | 7 +++++--
> drivers/iio/adc/qcom-spmi-iadc.c | 4 +++-
> drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 7 +++++--
> 3 files changed, 13 insertions(+), 5 deletions(-)
> ---
> base-commit: a4cda136f021ad44b8b52286aafd613030a6db5f
> change-id: 20250406-b4-device-wakeup-leak-iio-4457b99b6a91
>
> Best regards,
prev parent reply other threads:[~2025-04-12 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 20:01 [PATCH 0/3] iio: Fix wakeup source leaks on device unbind Krzysztof Kozlowski
2025-04-06 20:01 ` [PATCH 1/3] iio: accel: fxls8962af: " Krzysztof Kozlowski
2025-04-06 20:01 ` [PATCH 2/3] iio: adc: qcom-spmi-iadc: " Krzysztof Kozlowski
2025-04-06 20:01 ` [PATCH 3/3] iio: imu: st_lsm6dsx: " Krzysztof Kozlowski
2025-04-08 7:05 ` Lorenzo Bianconi
2025-04-12 11:24 ` 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=20250412122454.2a34182b@jic23-huawei \
--to=jic23@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-arm-msm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox