linux-kernel - Re: [PATCH v3 4/6] spi: spi-fsl-dspi: Use non-coherent memory for DMA

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <aF0sKdrQercCEDgB@finisterre.sirena.org.uk>
Date: Thu, 26 Jun 2025 12:16:57 +0100
From: Mark Brown <broonie@...nel.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: James Clark <james.clark@...aro.org>, Frank Li <Frank.li@....com>,
	Vladimir Oltean <olteanv@...il.com>,
	Vladimir Oltean <vladimir.oltean@....com>,
	Larisa Grigore <larisa.grigore@....com>,
	Christoph Hellwig <hch@....de>, linux-spi@...r.kernel.org,
	imx@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 4/6] spi: spi-fsl-dspi: Use non-coherent memory for DMA

On Thu, Jun 26, 2025 at 11:38:46AM +0200, Arnd Bergmann wrote:

> If you submit your changes as a pull request for inclusion, the
> common solution is to put the cover letter into the signed tag,
> which then gets used as both the description in 'git request-pull'
> and in the merge commit.

That does rely on the maintainer taking the changes as a pull request
which you probably shouldn't expect without some prior discussion.

> See e.g. commit 5b31d2d81a4b ("spi: sh-msiof: Transfer size
> improvements and I2S") for how a similar series on another driver
> shows up in the git log.

That's not a pull request - for my CI I generally apply serieses on a
separate branch then if they pass merge them into my branch.  If they
need a merge commit I use the cover letter to generate content for that.

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