linux-kernel - Re: [PATCH] spi: loopback-test: fix up const pointer issue in rx_ranges

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: <174792108209.84499.17148093262330532612.b4-ty@kernel.org>
Date: Thu, 22 May 2025 14:38:02 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, 
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: loopback-test: fix up const pointer issue in
 rx_ranges_cmp()

On Thu, 22 May 2025 12:59:14 +0200, Greg Kroah-Hartman wrote:
> When a list head is a const pointer, the list entry for that head also
> must remain a const pointer, otherwise we are just "throwing it away"
> for no good reason.  Fix this up by properly marking these structures as
> const.
> 
> 

Applied to

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

Thanks!

[1/1] spi: loopback-test: fix up const pointer issue in rx_ranges_cmp()
      commit: e7f3d11567c2c79c4342791ba91c500b434ce147

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