linux-kernel - Re: [PATCH v1 1/1] spi: spidev: Use SPI_MODE_USER

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: <163768666726.1388476.11718279194714572718.b4-ty@kernel.org>
Date:   Tue, 23 Nov 2021 16:57:47 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/1] spi: spidev: Use SPI_MODE_USER_MASK instead of casting

On Mon, 22 Nov 2021 19:52:45 +0200, Andy Shevchenko wrote:
> Currently the 16-bit mode is what being used in user space.
> However assuming that is not fully correct. Instead we should
> use the respective mask, i.e. SPI_MODE_USER_MASK, which
> precisely defines what bits are available for user space apps.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spidev: Use SPI_MODE_USER_MASK instead of casting
      commit: dd06a0c6b6f64f6610c0bb8f7651df3ebfb0f990

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