public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
	"Marek Vasut" <marek.vasut+renesas@gmail.com>,
	"Bartosz Golaszewski" <brgl@kernel.org>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"André Draszik" <andre.draszik@linaro.org>,
	"Douglas Anderson" <dianders@chromium.org>,
	linux-kernel@vger.kernel.org, "Johan Hovold" <johan@kernel.org>
Subject: [PATCH v2 0/7] regulator: fix OF node imbalance on reuse
Date: Wed,  8 Apr 2026 09:30:48 +0200	[thread overview]
Message-ID: <20260408073055.5183-1-johan@kernel.org> (raw)

These drivers reuse the OF node of their parent multi-function device
but fail to take another reference to balance the one dropped by the
platform bus code when unbinding the MFD and deregistering the child
devices.
	        
Fix this by using the intended helper for reusing OF nodes.

Note that the first two patches will cause a trivial conflict with Doug's
series adding accessor functions for struct device flags which has now been
merged to the driver-core tree:

	https://lore.kernel.org/r/20260406232444.3117516-1-dianders@chromium.org

Johan


Changes in v2:
 - use the correct rk808 Fixes tag
 - merge all the fixes into one series


Johan Hovold (7):
  regulator: bq257xx: fix OF node reference imbalance
  regulator: rk808: fix OF node reference imbalance
  regulator: max77650: fix OF node reference imbalance
  regulator: mt6357: fix OF node reference imbalance
  regulator: s2dos05: fix OF node reference imbalance
  regulator: act8945a: fix OF node reference imbalance
  regulator: bd9571mwv: fix OF node reference imbalance

 drivers/regulator/act8945a-regulator.c  | 3 ++-
 drivers/regulator/bd9571mwv-regulator.c | 3 ++-
 drivers/regulator/bq257xx-regulator.c   | 3 +--
 drivers/regulator/max77650-regulator.c  | 2 +-
 drivers/regulator/mt6357-regulator.c    | 2 +-
 drivers/regulator/rk808-regulator.c     | 3 +--
 drivers/regulator/s2dos05-regulator.c   | 2 +-
 7 files changed, 9 insertions(+), 9 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-04-08  7:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08  7:30 Johan Hovold [this message]
2026-04-08  7:30 ` [PATCH v2 1/7] regulator: bq257xx: fix OF node reference imbalance Johan Hovold
2026-04-08  7:30 ` [PATCH v2 2/7] regulator: rk808: " Johan Hovold
2026-04-08  7:30 ` [PATCH v2 3/7] regulator: max77650: " Johan Hovold
2026-04-08  7:30 ` [PATCH v2 4/7] regulator: mt6357: " Johan Hovold
2026-04-08  7:30 ` [PATCH v2 5/7] regulator: s2dos05: " Johan Hovold
2026-04-08  7:30 ` [PATCH v2 6/7] regulator: act8945a: " Johan Hovold
2026-04-08  7:30 ` [PATCH v2 7/7] regulator: bd9571mwv: " Johan Hovold
2026-04-08 16:56 ` [PATCH v2 0/7] regulator: fix OF node imbalance on reuse Mark Brown

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=20260408073055.5183-1-johan@kernel.org \
    --to=johan@kernel.org \
    --cc=andre.draszik@linaro.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=brgl@kernel.org \
    --cc=broonie@kernel.org \
    --cc=dianders@chromium.org \
    --cc=krzk@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=matthias.bgg@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