linux-kernel - Re: [PATCH v2 1/3] spi: atmel: simplify MR register update in cs

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: <175499674908.16293.5097516304989126078.b4-ty@kernel.org>
Date: Tue, 12 Aug 2025 12:05:49 +0100
From: Mark Brown <broonie@...nel.org>
To: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, 
 nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com, 
 claudiu.beznea@...on.dev, ryan.wanner@...rochip.com, 
 tudor.ambarus@...aro.org, linux-spi@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 linux-kernel@...r.kernel.org, 
 Manikandan Muralidharan <manikandan.m@...rochip.com>
Subject: Re: [PATCH v2 1/3] spi: atmel: simplify MR register update in
 cs_activate()

On Wed, 30 Jul 2025 15:40:13 +0530, Manikandan Muralidharan wrote:
> simplified the MR register configuration by updating only the PCS field
> using SPI_BFINS() instead of rewriting the entire register.
> Avoids code duplication.
> 
> 

Applied to

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

Thanks!

[1/3] spi: atmel: simplify MR register update in cs_activate()
      commit: 379f819733f28b5aa1802f3ede442f08b7275f4e
[2/3] spi: dt-bindings: atmel,at91rm9200-spi: Add support for optional 'spi_gclk' clock
      commit: a673ebd0a2a587f3d6b923d59d363fc9e8a9f920
[3/3] spi: atmel: Add support for handling GCLK as a clock source
      commit: 91e5722baaea06c1f1b105e9e3fd6645dbdd938b

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