From: Lee Jones <lee@kernel.org>
To: Karel Balej <balejk@matfyz.cz>, Lee Jones <lee@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] mfd: Fix wakeup source leaks on device unbind
Date: Thu, 08 May 2025 15:14:16 +0100 [thread overview]
Message-ID: <174671365657.2459720.504749254225457244.b4-ty@kernel.org> (raw)
In-Reply-To: <20250406-mfd-device-wakekup-leak-v1-0-318e14bdba0a@linaro.org>
On Sun, 06 Apr 2025 21:50:08 +0200, Krzysztof Kozlowski wrote:
> Device can be unbound, so driver must also release memory for the wakeup
> source. Use devm for driver already having devm interface and manually
> disable wakeup for drivers still having remove() callback to keep
> consistent ordering of cleanups.
>
> I did not update the drivers with suppress_bind_attrs and no error paths
> after device_init_wakeup() because it would not bring any benefits.
>
> [...]
Applied, thanks!
[1/8] mfd: 88pm886: Fix wakeup source leaks on device unbind
commit: 0fcb3bee6f9e004b1d52ad6e090bcd0ff2cc7add
[2/8] mfd: as3722: Fix wakeup source leaks on device unbind
commit: 16e0c58e342867fec5198fbd0af7f93f49d12f42
[3/8] mfd: max14577: Fix wakeup source leaks on device unbind
commit: add4c382ae0185ebdde685b5992efcc3052e487f
[4/8] mfd: max77541: Fix wakeup source leaks on device unbind
commit: e1b513336240d05e43fb4f0165e2ff242cc5c5aa
[5/8] mfd: max77705: Fix wakeup source leaks on device unbind
commit: ae3311e911012dc433ba79ef9d5cb6d3eb144223
[6/8] mfd: max8925: Fix wakeup source leaks on device unbind
commit: a58fa75ee660144620e42abeffd517c6dab40ce7
[7/8] mfd: rt5033: Fix wakeup source leaks on device unbind
commit: c85164efc5486eb711b376a15aecfd37c292c09f
[8/8] mfd: sprd-sc27xx: Fix wakeup source leaks on device unbind
commit: 7f8bb8ef012ee27b601b778b3ef33223f242604f
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-05-08 14:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 19:50 Krzysztof Kozlowski
2025-04-06 19:50 ` [PATCH 1/8] mfd: 88pm886: " Krzysztof Kozlowski
2025-04-08 13:45 ` Karel Balej
2025-04-06 19:50 ` [PATCH 2/8] mfd: as3722: " Krzysztof Kozlowski
2025-04-06 19:50 ` [PATCH 3/8] mfd: max14577: " Krzysztof Kozlowski
2025-04-15 15:49 ` Lee Jones
2025-04-06 19:50 ` [PATCH 4/8] mfd: max77541: " Krzysztof Kozlowski
2025-04-06 19:50 ` [PATCH 5/8] mfd: max77705: " Krzysztof Kozlowski
2025-04-06 19:50 ` [PATCH 6/8] mfd: max8925: " Krzysztof Kozlowski
2025-04-15 15:48 ` Lee Jones
2025-05-01 15:17 ` Krzysztof Kozlowski
2025-04-06 19:50 ` [PATCH 7/8] mfd: rt5033: " Krzysztof Kozlowski
2025-04-06 19:50 ` [PATCH 8/8] mfd: sprd-sc27xx: " Krzysztof Kozlowski
2025-04-07 1:56 ` Baolin Wang
2025-05-08 14:14 ` Lee Jones [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=174671365657.2459720.504749254225457244.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=balejk@matfyz.cz \
--cc=baolin.wang@linux.alibaba.com \
--cc=cw00.choi@samsung.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@gmail.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
all inboxes | Powered by JetHome®