From: Francesco Dolcini <francesco@dolcini.it>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Shree Ramamoorthy <s-ramamoorthy@ti.com>,
Francesco Dolcini <francesco@dolcini.it>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH] regulator: tps65219: fix irq_data.rdev not being assigned
Date: Thu, 14 May 2026 10:48:18 +0200 [thread overview]
Message-ID: <agWMUrNZjscW2JtT@gaggiata.pivistrello.it> (raw)
In-Reply-To: <20260513160706.1096845-1-alexander.sverdlin@siemens.com>
Hello Alexander,
thanks for the patch
On Wed, May 13, 2026 at 06:07:04PM +0200, A. Sverdlin wrote:
...
> Internal error: Oops: 0000000096000004
> pc : regulator_notifier_call_chain
> lr : tps65219_regulator_irq_handler
> Call trace:
> regulator_notifier_call_chain
> tps65219_regulator_irq_handler
> handle_nested_irq
> regmap_irq_thread
> irq_thread_fn
> irq_thread
> kthread
> ret_from_fork
...
> Link: https://lore.kernel.org/all/aBDSTxALaOc-PD7X@gaggiata.pivistrello.it/
> Fixes: 64a6b577490c ("regulator: tps65219: Remove debugging helper function")
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Is this a fix for the issue I reported long ago? If yes, it should be
Reported-by: Francesco...
Closes: https://lore.kernel.org/all/aBDSTxALaOc-PD7X@gaggiata.pivistrello.it/
Cc: stable...
and remove the Link:
Francesco
prev parent reply other threads:[~2026-05-14 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 16:07 [PATCH] regulator: tps65219: fix irq_data.rdev not being assigned A. Sverdlin
2026-05-14 8:48 ` Francesco Dolcini [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=agWMUrNZjscW2JtT@gaggiata.pivistrello.it \
--to=francesco@dolcini.it \
--cc=aaro.koskinen@iki.fi \
--cc=alexander.sverdlin@siemens.com \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=rogerq@kernel.org \
--cc=s-ramamoorthy@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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