From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: Peter Rosin <peda@axentia.se>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Andrew Davis <afd@ti.com>
Subject: Re: [PATCH] mux: mmio: fix regmap leak on probe failure
Date: Thu, 5 Feb 2026 17:07:53 +0100 [thread overview]
Message-ID: <2026020547-primp-dominion-cbc3@gregkh> (raw)
In-Reply-To: <aYNxOL6vqCm_UL0V@hovoldconsulting.com>
On Wed, Feb 04, 2026 at 05:18:00PM +0100, Johan Hovold wrote:
> Hi Greg and Peter,
>
> On Tue, Jan 27, 2026 at 04:56:15PM +0100, Johan Hovold wrote:
> > On Thu, Nov 27, 2025 at 02:47:02PM +0100, Johan Hovold wrote:
> > > The mmio regmap that may be allocated during probe is never freed.
> > >
> > > Switch to using the device managed allocator so that the regmap is
> > > released on probe failures (e.g. probe deferral) and on driver unbind.
> > >
> > > Fixes: 61de83fd8256 ("mux: mmio: Do not use syscon helper to build regmap")
> > > Cc: stable@vger.kernel.org # 6.16
> > > Cc: Andrew Davis <afd@ti.com>
> > > Signed-off-by: Johan Hovold <johan@kernel.org>
> > > ---
> >
> > Can this one be picked up for 6.20?
>
> This one has been sitting on the list for over two months now without
> any comment from Peter.
>
> I know there have been some issues in the past which patches for this
> subsystem not being picked up, so perhaps you could just take this one
> directly, Greg?
>
> It's been reviewed by Andrew.
>
> Johan
Now taken, thanks.,
greg k-h
prev parent reply other threads:[~2026-02-05 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 13:47 [PATCH] mux: mmio: fix regmap leak on probe failure Johan Hovold
2025-12-01 18:02 ` Andrew Davis
2026-01-27 15:56 ` Johan Hovold
2026-02-04 16:18 ` Johan Hovold
2026-02-05 16:07 ` Greg Kroah-Hartman [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=2026020547-primp-dominion-cbc3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=afd@ti.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--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 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.