linux-kernel - Re: [PATCH] spi: fsl-spi: Remove display of virtual address

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: <173643003851.53058.4009453720979125010.b4-ty@kernel.org>
Date: Thu, 09 Jan 2025 13:40:38 +0000
From: Mark Brown <broonie@...nel.org>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, 
 linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: fsl-spi: Remove display of virtual address

On Thu, 09 Jan 2025 07:51:45 +0100, Christophe Leroy wrote:
> The following appears in kernel log at boot:
> 
> 	fsl_spi b01004c0.spi: at 0x(ptrval) (irq = 51), QE mode
> 
> This is useless, so remove the display of that virtual address and
> display the MMIO address instead, just like serial core does.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: fsl-spi: Remove display of virtual address
      commit: 636ee5781d259258dc9425a5552be1ffa458633c

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