linux-kernel - Re: [PATCH v2] spi: spidev: mask SPI_CS_HIGH in SPI_IOC_RD

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: <166989722460.51770.10306865955745986625.b4-ty@kernel.org>
Date:   Thu, 01 Dec 2022 12:20:24 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org,
        "A. Sverdlin" <alexander.sverdlin@...mens.com>
Cc:     linux-kernel@...r.kernel.org,
        Linus Walleij <linus.walleij@...aro.org>,
        Lukas Wunner <lukas@...ner.de>
Subject: Re: [PATCH v2] spi: spidev: mask SPI_CS_HIGH in SPI_IOC_RD_MODE

On Wed, 30 Nov 2022 17:29:27 +0100, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@...mens.com>
> 
> Commit f3186dd87669 ("spi: Optionally use GPIO descriptors for CS GPIOs")
> has changed the user-space interface so that bogus SPI_CS_HIGH started
> to appear in the mask returned by SPI_IOC_RD_MODE even for active-low CS
> pins. Commit 138c9c32f090
> ("spi: spidev: Fix CS polarity if GPIO descriptors are used") fixed only
> SPI_IOC_WR_MODE part of the problem. Let's fix SPI_IOC_RD_MODE
> symmetrically.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spidev: mask SPI_CS_HIGH in SPI_IOC_RD_MODE
      commit: 7dbfa445ff7393d1c4c066c1727c9e0af1251958

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