[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <43194819-3aea-4541-900d-381fb27ebcc9@prolan.hu>
Date: Fri, 17 Jan 2025 17:58:11 +0100
From: Csókás Bence <csokas.bence@...lan.hu>
To: Mark Brown <broonie@...nel.org>
CC: <linux-spi@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, Nicolas Ferre <nicolas.ferre@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>, Claudiu Beznea
<claudiu.beznea@...on.dev>
Subject: Re: [PATCH 3/4] spi: atmel-quadspi: Use `devm_dma_request_chan()`
Hi,
On 2025. 01. 15. 20:58, Mark Brown wrote:
> On Wed, Jan 15, 2025 at 05:02:40PM +0100, Bence Csókás wrote:
>> Leave releasing of DMA channels up to the devm
>> facilities. This way we can eliminate the rest
>> of the "goto ladder".
>
> You've not copied me on the rest of the series so I don't know what's
> going on with dependencies. When sending a patch series it is important
> to ensure that all the various maintainers understand what the
> relationship between the patches as the expecation is that there will be
> interdependencies. Either copy everyone on the whole series or at least
> copy them on the cover letter and explain what's going on. If there are
> no strong interdependencies then it's generally simplest to just send
> the patches separately to avoid any possible confusion.
I did not originally create a cover letter, but now I made one, that
should make it clearer, that this series is mainly about the 3rd and 4th
patch, sent to you and the SPI list, and the former two only add the new
APIs they use, to the respective subsystems.
Bence
Powered by blists - more mailing lists