linux-kernel - Re: [PATCH] spi: spi-cadence: Fix SPI NO Slave Select macro definition

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: <165835123856.909862.1674350119538638.b4-ty@kernel.org>
Date:   Wed, 20 Jul 2022 22:07:18 +0100
From:   Mark Brown <broonie@...nel.org>
To:     amit.kumar-mahapatra@...inx.com
Cc:     git@....com, linux-spi@...r.kernel.org,
        lakshmi.sai.krishna.potthuri@...inx.com,
        linux-kernel@...r.kernel.org, amit.kumar-mahapatra@....com,
        sai.krishna.potthuri@....com
Subject: Re: [PATCH] spi: spi-cadence: Fix SPI NO Slave Select macro definition

On Wed, 13 Jul 2022 22:15:29 +0530, Amit Kumar Mahapatra wrote:
> From: Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@...inx.com>
> 
> Fix SPI NO Slave Select macro definition, when all the SPI CS bits
> are high which means no slave is selected.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi-cadence: Fix SPI NO Slave Select macro definition
      commit: e1502ba41699736c578ba9d61ae6285d49f6921b

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