linux-kernel - Re: [PATCH v1 1/1] spi: microchip-core: use XOR instead of ANDNOT to fix the logic

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: <176797261111.67850.5868118938886891604.b4-ty@kernel.org>
Date: Fri, 09 Jan 2026 15:30:11 +0000
From: Mark Brown <broonie@...nel.org>
To: Prajna Rajendra Kumar <prajna.rajendrakumar@...rochip.com>, 
 linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v1 1/1] spi: microchip-core: use XOR instead of ANDNOT
 to fix the logic

On Thu, 08 Jan 2026 18:49:40 +0100, Andy Shevchenko wrote:
> Use XOR instead of ANDNOT to fix the logic. The current approach with
> (foo & BAR & ~baz) is harder to process, and it proved to be wrong,
> than more usual pattern for the comparing misconfiguration using
> ((foo ^ baz) & BAR) which can be read as "find all different bits
> between foo and baz that are related to BAR (mask)". Besides that
> it makes the binary code shorter.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: microchip-core: use XOR instead of ANDNOT to fix the logic
      commit: 19a4505a7a5d4eea70f1a42d601c25d730922fdf

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