[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aRw8tWOmXhivruFW@hovoldconsulting.com>
Date: Tue, 18 Nov 2025 10:30:29 +0100
From: Johan Hovold <johan@...nel.org>
To: Vladimir Zapolskiy <vz@...ia.com>
Cc: Vinod Koul <vkoul@...nel.org>,
Ludovic Desroches <ludovic.desroches@...rochip.com>,
Viresh Kumar <vireshk@...nel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Vinicius Costa Gomes <vinicius.gomes@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Piotr Wojtaszczyk <piotr.wojtaszczyk@...esys.com>,
Amélie Delaunay <amelie.delaunay@...s.st.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Peter Ujfalusi <peter.ujfalusi@...il.com>,
dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH 06/15] dmaengine: lpc18xx-dmamux: fix device leak on
route allocation
Hi Vladimir,
On Mon, Nov 17, 2025 at 09:24:48PM +0200, Vladimir Zapolskiy wrote:
> On 11/17/25 18:12, Johan Hovold wrote:
> > Make sure to drop the reference taken when looking up the DMA mux
> > platform device during route allocation.
> >
> > Note that holding a reference to a device does not prevent its driver
> > data from going away so there is no point in keeping the reference.
> >
> > Fixes: e5f4ae84be74 ("dmaengine: add driver for lpc18xx dmamux")
> > Cc: stable@...r.kernel.org # 4.3
> > Signed-off-by: Johan Hovold <johan@...nel.org>
> Reviewed-by: Vladimir Zapolskiy <vz@...ia.com>
Thanks for reviewing.
Johan
Powered by blists - more mailing lists