From: Mark Brown <broonie@kernel.org>
To: "Csókás Bence" <csokas.bence@prolan.hu>
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:36:01 +0200 [thread overview]
Message-ID: <aCW1geupMxr8Ft_k@finisterre.sirena.org.uk> (raw)
In-Reply-To: <9d384301-3f73-4120-a82b-580eb5f1a4ed@prolan.hu>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
On Thu, May 15, 2025 at 11:26:57AM +0200, Csókás Bence wrote:
> On 2025. 05. 15. 11:22, Mark Brown wrote:
> > Wouldn't it be simpler for me to just apply both
> > patches at this point if there's no conflicts with the DMA tree? We're
> > at -rc6 now...
> That also works for me. I should send 1/2 to you as well, correct?
I think at this point with the merge window likely to open on Sunday
it's probably easiest to just resend the SPI patch after the merge
window, it'll likely take more time/effort to work out what to do than
it will for the reset changes to land in Linus' tree.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-05-15 9:36 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
2025-05-15 9:22 ` Mark Brown
2025-05-15 9:26 ` Csókás Bence
2025-05-15 9:36 ` Mark Brown [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=aCW1geupMxr8Ft_k@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=csokas.bence@prolan.hu \
--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®