linux-kernel - Re: [PATCH] spi: reorder spi_message struct member doc comments

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: <170679517864.44749.10082747405846291000.b4-ty@kernel.org>
Date: Thu, 01 Feb 2024 13:46:18 +0000
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: reorder spi_message struct member doc comments

On Wed, 31 Jan 2024 11:07:27 -0600, David Lechner wrote:
> The members of `struct spi_message` were reordered in commit
> ae2ade4ba581 ("spi: Reorder fields in 'struct spi_message'")
> but the documentation comments were not updated to match.
> 
> This commit updates the comments to match the new order.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: reorder spi_message struct member doc comments
      commit: e6c5812dc4d0b3e890608cb9c98597d1bed7e937

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