linux-kernel - Re: [PATCH 3/4] spi: atmel-quadspi: Use `devm_dma_request

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c0bf43cf-895c-4a0e-b771-39481b6bc024@sirena.org.uk>
Date: Wed, 15 Jan 2025 19:58:08 +0000
From: Mark Brown <broonie@...nel.org>
To: Bence Csókás <csokas.bence@...lan.hu>
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()`

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.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)