linux-kernel - Re: [PATCH] spi: spidev_test: Warn when the mode is not the requested 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: <165514107437.671611.16068844407175899226.b4-ty@kernel.org>
Date:   Mon, 13 Jun 2022 18:24:34 +0100
From:   Mark Brown <broonie@...nel.org>
To:     David@...es.net
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: spidev_test: Warn when the mode is not the requested mode

On Mon, 13 Jun 2022 00:39:41 -0500, David Fries wrote:
> Print a warning if the device mode doesn't match the requested mode.
> The user doesn't enter the mode in hex so it isn't obvious when
> setting the mode succeeds that the mode isn't the requested mode.  The
> kernel logs a message, it will be more visible if the test also prints
> a warning.  I was testing --quad, which is unsupported, but doesn't
> cause the mode request to fail.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spidev_test: Warn when the mode is not the requested mode
      commit: 41ecad2c3cce807abf32bff879cef5dfcacae363

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