From: Sasha Levin <sashal@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
stable-commits@vger.kernel.org,
Sebastian Reichel <sre@kernel.org>
Subject: Re: Patch "power: supply: core: implement extension API" has been added to the 6.12-stable tree
Date: Wed, 18 Nov 2026 07:39:57 -0500 [thread overview]
Message-ID: <20261118124002.3727477-1-sashal@kernel.org> (raw)
In-Reply-To: <6ffbbf17-c105-4ff3-94bb-ede950f574c2@t-8ch.de>
On Wed, Nov 18, 2026 at 09:47:41AM +0000, Thomas Weißschuh wrote:
> This feature backport should not be necessary.
Dropped the extension API backports from the 6.12 queue again, together with
5b4bd13e0552 ("power: supply: core: prevent unregistering a power supply while
a callback runs") and 9f7f7a859451 ("power_supply: serialize property access
with unregister"), which is what pulled them in this time.
9f7f7a859451 is also dropped from the 7.3 and 6.18 queues for now, because with
it mt6370-charger, qcom_smbx and cpcap-battery call power_supply_get_property()
on their own supply from inside a callback and so take epc_sem for read
recursively, which can hang power_supply_unregister(). Mainline has the same
code.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-18 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261117173125.2151200-1-sashal@kernel.org>
2026-11-18 9:47 ` Patch "power: supply: core: implement extension API" has been added to the 6.12-stable tree Thomas Weißschuh
2026-11-18 12:39 ` Sasha Levin [this message]
[not found] <20261021115355.4175993-1-sashal@kernel.org>
2026-10-21 12:37 ` Thomas Weißschuh
2026-10-23 20:02 ` Sasha Levin
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=20261118124002.3727477-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=linux@weissschuh.net \
--cc=sre@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.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