linux-kernel - Re: [PATCH] spi: loopback-test: Do not split 1024-byte hexdumps

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: <174648879977.4120313.11711906225313425747.b4-ty@kernel.org>
Date: Tue, 06 May 2025 08:46:39 +0900
From: Mark Brown <broonie@...nel.org>
To: Martin Sperl <kernel@...tin.sperl.org>, 
 Geert Uytterhoeven <geert+renesas@...der.be>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: loopback-test: Do not split 1024-byte hexdumps

On Fri, 02 May 2025 13:10:35 +0200, Geert Uytterhoeven wrote:
> spi_test_print_hex_dump() prints buffers holding less than 1024 bytes in
> full.  Larger buffers are truncated: only the first 512 and the last 512
> bytes are printed, separated by a truncation message.  The latter is
> confusing in case the buffer holds exactly 1024 bytes, as all data is
> printed anyway.
> 
> Fix this by printing buffers holding up to and including 1024 bytes in
> full.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: loopback-test: Do not split 1024-byte hexdumps
      commit: a73fa3690a1f3014d6677e368dce4e70767a6ba2

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