linux-kernel - Re: [PATCH] spi: sophgo: Fix incorrect use of bus width value macros

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: <176355176717.1842480.2581189762580750444.b4-ty@kernel.org>
Date: Wed, 19 Nov 2025 11:29:27 +0000
From: Mark Brown <broonie@...nel.org>
To: Chen Wang <unicorn_wang@...look.com>, 
 Inochi Amaoto <inochiama@...il.com>, Longbin Li <looong.bin@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 sophgo@...ts.linux.dev
Subject: Re: [PATCH] spi: sophgo: Fix incorrect use of bus width value
 macros

On Mon, 17 Nov 2025 17:05:39 +0800, Longbin Li wrote:
> The previous code initialized the 'reg' value with specific bus-width
> values (BUS_WIDTH_2_BIT and BUS_WIDTH_4_BIT), which introduces ambiguity.
> Replace them with BUS_WIDTH_MASK to express the intention clearly.
> 
> 

Applied to

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

Thanks!

[1/1] spi: sophgo: Fix incorrect use of bus width value macros
      commit: d9813cd23d5a7b254cc1b1c1ea042634d8da62e6

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