linux-kernel - Re: [PATCH v2 1/2] spi: Allow to have all native CSs in use along with GPIOs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <161903040536.13608.17759253372901499681.b4-ty@kernel.org>
Date:   Wed, 21 Apr 2021 20:03:24 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v2 1/2] spi: Allow to have all native CSs in use along with GPIOs

On Tue, 20 Apr 2021 19:44:24 +0300, Andy Shevchenko wrote:
> The commit 7d93aecdb58d ("spi: Add generic support for unused native cs
> with cs-gpios") excludes the valid case for the controllers that doesn't
> need to switch native CS in order to perform the transfer, i.e. when
> 
>   0		native
>   ...		...
>   <n> - 1	native
>   <n>		GPIO
>   <n> + 1	GPIO
>   ...		...
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: Allow to have all native CSs in use along with GPIOs
      commit: dbaca8e56ea3f23fa215f48c2d46dd03ede06e02
[2/2] spi: Avoid undefined behaviour when counting unused native CSs
      commit: f60d7270c8a3d2beb1c23ae0da42497afa3584c2

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