linux-kernel - Re: [PATCH] spi: atmel-quadspi: Update to current device naming terminology

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: <173643003976.53058.4013563877112652106.b4-ty@kernel.org>
Date: Thu, 09 Jan 2025 13:40:39 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, Alexander Dahl <ada@...rsis.com>
Cc: Tudor Ambarus <tudor.ambarus@...aro.org>, 
 Varshini Rajendran <varshini.rajendran@...rochip.com>, 
 Bence Csókás <csokas.bence@...lan.hu>, 
 Nicolas Ferre <nicolas.ferre@...rochip.com>, 
 Alexandre Belloni <alexandre.belloni@...tlin.com>, 
 Claudiu Beznea <claudiu.beznea@...on.dev>, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: atmel-quadspi: Update to current device naming
 terminology

On Thu, 09 Jan 2025 10:48:43 +0100, Alexander Dahl wrote:
> For v6.9 the spi subsystem changed the terminology to host and target
> devices, see commit 99769a52464d ("spi: Update the "master/slave"
> terminology in documentation") for reference.  Support for SAMA7G5 was
> forward ported recently from an old vendor branch before that
> terminology change, so naming for the new struct member is adapted to
> follow the current scheme.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: atmel-quadspi: Update to current device naming terminology
      commit: 5e56618e1593a9eb9d72dc9433ac7a02a6c48c8f

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark