linux-kernel - Re: [PATCH] spi: use spi_valid_{tx,rx}buf() in stats function

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: <171457161096.1895134.6406701144807353881.b4-ty@kernel.org>
Date: Wed, 01 May 2024 22:53:30 +0900
From: Mark Brown <broonie@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: use spi_valid_{tx,rx}buf() in stats function

On Tue, 30 Apr 2024 15:15:27 -0500, David Lechner wrote:
> There are macros spi_valid_txbuf() and spi_valid_rxbuf() for determining
> if an xfer actually intended to send or receive data.
> 
> These checks were hard-coded in spi_statistics_add_transfer_stats(). We
> can make use of the macros instead to make the code more readable and
> more robust against potential future changes in case the definition of
> what valid means changes.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: use spi_valid_{tx,rx}buf() in stats function
      commit: 52267fe8456a2a05f70b29d68292eec789c960b9

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