From: "Csókás Bence" <csokas.bence@prolan.hu>
To: Mark Brown <broonie@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-spi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
"Vinod Koul" <vkoul@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>
Subject: Re: [PATCH v6 0/2] Add `devm_dma_request_chan()` to simplify probe path in atmel-quadspi.c
Date: Thu, 15 May 2025 11:14:22 +0200 [thread overview]
Message-ID: <e4e6c7a9-9b7a-4012-8bda-75804229ec95@prolan.hu> (raw)
In-Reply-To: <aCWpjplhAXUvr9fj@finisterre.sirena.org.uk>
Hi,
On 2025. 05. 15. 10:45, Mark Brown wrote:
> 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.
Yes, the situation is a bit convoluted. Obviously 2/2 will be applied
after 1/2, in a similar vein than the former PM series.
So what I was trying to say: Vinod should be able to apply 1/2 to his
branch (dma/next) right now, which can then be merged to spi/for-next.
This merged branch should be able to then cleanly apply 2/2.
Bence
next prev parent reply other threads:[~2025-05-15 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 8:31 Bence Csókás
2025-05-15 8:31 ` [PATCH v6 1/2] dma: Add devm_dma_request_chan() Bence Csókás
2025-05-15 8:31 ` [PATCH v6 2/2] spi: atmel-quadspi: Use `devm_dma_request_chan()` Bence Csókás
2025-05-15 8:45 ` [PATCH v6 0/2] Add `devm_dma_request_chan()` to simplify probe path in atmel-quadspi.c Mark Brown
2025-05-15 9:14 ` Csókás Bence [this message]
2025-05-15 9:22 ` Mark Brown
2025-05-15 9:26 ` Csókás Bence
2025-05-15 9:36 ` Mark Brown
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=e4e6c7a9-9b7a-4012-8bda-75804229ec95@prolan.hu \
--to=csokas.bence@prolan.hu \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=rafael@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=vkoul@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®