[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aCWpjplhAXUvr9fj@finisterre.sirena.org.uk>
Date: Thu, 15 May 2025 10:45:02 +0200
From: Mark Brown <broonie@...nel.org>
To: Bence Csókás <csokas.bence@...lan.hu>
Cc: dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Vinod Koul <vkoul@...nel.org>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Claudiu Beznea <claudiu.beznea@...on.dev>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Tudor Ambarus <tudor.ambarus@...aro.org>
Subject: Re: [PATCH v6 0/2] Add `devm_dma_request_chan()` to simplify probe
path in atmel-quadspi.c
On Thu, May 15, 2025 at 10:31:28AM +0200, Bence Csókás wrote:
> Change in v4:
> * split PM imbalance fix (now merged) and DMA cleanup (this series)
> Change in v6:
> * rebase to spi/for-next, see note below:
>
> There is currently no difference in drivers/dma/dmaengine.c between it and
> dma/next [1], therefore PATCH 1/2 should be safe for Vinod to apply. But
> this way PATCH 2/2 is trivial to apply. I didn't want to pull the whole
> linux-next tree, but if any ofyou run into problems, let me know, and I'll
> rebase the series on it instead.
I can't tell what the plan is here, or what the status is for the first
patch (since I'm not CCed). The second patch depends on a new API
introduced in the first patch so it can't be merged independently.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists