All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: sre@kernel.org, Hans de Goede <hansg@kernel.org>,
	 Armin Wolf <W_Armin@gmx.de>
Cc: linux-pm@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] power: supply: core: Add power_supply_get/set_property_direct()
Date: Mon, 07 Jul 2025 16:00:04 +0300	[thread overview]
Message-ID: <175189320409.2280.2456749792554779164.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250627205124.250433-1-W_Armin@gmx.de>

On Fri, 27 Jun 2025 22:51:22 +0200, Armin Wolf wrote:

> Power supply extensions might want to interact with the underlying
> power supply to retrieve data like serial numbers, charging status
> and more. However doing so causes psy->extensions_sem to be locked
> twice, possibly causing a deadlock.
> 
> Provide special variants of power_supply_get/set_property() that
> ignore any power supply extensions and thus do not touch the
> associated psy->extensions_sem lock.
> 
> [...]


Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.

The list of commits applied:
[1/3] power: supply: core: Add power_supply_get/set_property_direct()
      commit: 3ebed2fddf6fac5729ffc8c471c87d111b641678
[2/3] power: supply: test-power: Test access to extended power supply
      commit: a5f354232118751fe43be6ac896f8d6e7d7418b5
[3/3] platform/x86: dell-ddv: Fix taking the psy->extensions_sem lock twice
      commit: d4e83784b2a9be58b938d55efb232d2751c4cab4

--
 i.


  parent reply	other threads:[~2025-07-07 13:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 20:51 [PATCH 1/3] power: supply: core: Add power_supply_get/set_property_direct() Armin Wolf
2025-06-27 20:51 ` [PATCH 2/3] power: supply: test-power: Test access to extended power supply Armin Wolf
2025-07-06 23:13   ` Sebastian Reichel
2025-06-27 20:51 ` [PATCH 3/3] platform/x86: dell-ddv: Fix taking the psy->extensions_sem lock twice Armin Wolf
2025-06-28  9:25 ` [PATCH 1/3] power: supply: core: Add power_supply_get/set_property_direct() Hans de Goede
2025-06-28 21:34   ` Armin Wolf
2025-06-30  8:58     ` Ilpo Järvinen
2025-07-06 23:14       ` Sebastian Reichel
2025-07-06 23:11 ` Sebastian Reichel
2025-07-07 13:00 ` Ilpo Järvinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-27 20:53 Armin Wolf
2025-06-27 20:55 ` Armin Wolf

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=175189320409.2280.2456749792554779164.b4-ty@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=W_Armin@gmx.de \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=sre@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.