linux-kernel - Re: [PATCH] spi: spi-sn-f-ospi: fix duplicate flag while assigning to mode

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: <167715760528.62178.6653469643907332364.b4-ty@kernel.org>
Date:   Thu, 23 Feb 2023 13:06:45 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Dhruva Gole <d-gole@...com>
Cc:     Vignesh Raghavendra <vigneshr@...com>,
        Pratyush Yadav <ptyadav@...zon.de>, linux-spi@...r.kernel.org,
        Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>,
        linux-kernel@...r.kernel.org, David Binderman <dcb314@...mail.com>,
        stable@...r.kernel.org
Subject: Re: [PATCH] spi: spi-sn-f-ospi: fix duplicate flag while assigning
 to mode_bits

On Thu, 23 Feb 2023 15:22:02 +0530, Dhruva Gole wrote:
> Replace the SPI_TX_OCTAL flag that appeared two time with SPI_RX_OCTAL
> in the chain of '|' operators while assigning to mode_bits
> 
> Fixes: 1b74dd64c861 ("spi: Add Socionext F_OSPI SPI flash controller driver")
> 
> Reported-by: David Binderman <dcb314@...mail.com>
> Link: https://lore.kernel.org/all/DB6P189MB0568F3BE9384315F5C8C1A3E9CA49@DB6P189MB0568.EURP189.PROD.OUTLOOK.COM/
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-sn-f-ospi: fix duplicate flag while assigning to mode_bits
      commit: 078a5517d22342eb0474046d3e891427a2552e3c

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