linux-kernel - Re: [PATCH] spi: sunplus: sp7021: Clean up coding style

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: <175499674777.16293.15470606723953307689.b4-ty@kernel.org>
Date: Tue, 12 Aug 2025 12:05:47 +0100
From: Mark Brown <broonie@...nel.org>
To: lhjeff911@...il.com, "Darshan R." <rathod.darshan.0896@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: sunplus: sp7021: Clean up coding style

On Mon, 28 Jul 2025 12:41:04 +0000, Darshan R. wrote:
> This patch tidies up minor coding style deviations within the Sunplus SP7021 SPI driver, ensuring closer adherence to established kernel coding guidelines.
> 
> Specifically, it addresses:
> - Correction of a whitespace inconsistency before a comma in `writel()` calls.
> - Alignment of function parameter indentation for `struct spi_transfer *xfer` in `sp7021_spi_host_transfer_one()` and `sp7021_spi_target_transfer_one()`.
> 
> While purely cosmetic, these adjustments contribute to improved code readability and maintainability, making future development and review easier.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: sunplus: sp7021: Clean up coding style
      commit: f1ac30a862cc5d53392d59f42b513e79948acb18

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