mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
	 Douglas Anderson <dianders@chromium.org>,
	 Christian Eggers <ceggers@arri.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] regulator: dummy: force synchronous probing
Date: Tue, 11 Mar 2025 19:17:44 +0000	[thread overview]
Message-ID: <174172066480.347000.17075085482466373426.b4-ty@kernel.org> (raw)
In-Reply-To: <20250311091803.31026-1-ceggers@arri.de>

On Tue, 11 Mar 2025 10:18:02 +0100, Christian Eggers wrote:
> Sometimes I get a NULL pointer dereference at boot time in kobject_get()
> with the following call stack:
> 
> anatop_regulator_probe()
>  devm_regulator_register()
>   regulator_register()
>    regulator_resolve_supply()
>     kobject_get()
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/2] regulator: dummy: force synchronous probing
      commit: 8619909b38eeebd3e60910158d7d68441fc954e9
[2/2] regulator: check that dummy regulator has been probed before using it
      commit: b60ef2a3334ca15f249188870fc029ddf06ef7c4

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


  parent reply	other threads:[~2025-03-11 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  9:18 Christian Eggers
2025-03-11  9:18 ` [PATCH v2 2/2] regulator: check that dummy regulator has been probed before using it Christian Eggers
2025-03-13  0:46   ` Doug Anderson
2025-03-13  7:40     ` Christian Eggers
2025-03-11 19:17 ` Mark Brown [this message]
2025-03-13  0:42 ` [PATCH v2 1/2] regulator: dummy: force synchronous probing Doug Anderson
2025-03-13  7:36   ` Christian Eggers

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=174172066480.347000.17075085482466373426.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=ceggers@arri.de \
    --cc=dianders@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®