linux-kernel - Re: [PATCH] spi: nxp-fspi: make const array ls1028a_soc

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: <166741066762.302937.13190941938549227127.b4-ty@kernel.org>
Date:   Wed, 02 Nov 2022 17:37:47 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Yogesh Gaur <yogeshgaur.83@...il.com>, Han Xu <han.xu@....com>,
        linux-spi@...r.kernel.org, Haibo Chen <haibo.chen@....com>,
        Colin Ian King <colin.i.king@...il.com>
Cc:     kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: nxp-fspi: make const array ls1028a_soc_attr static

On Wed, 2 Nov 2022 15:29:04 +0000, Colin Ian King wrote:
> Don't populate the const array ls1028a_soc_attr on the stack, instead
> make it static. Also makes the object code smaller.
> 
> 

Applied to

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

Thanks!

[1/1] spi: nxp-fspi: make const array ls1028a_soc_attr static
      commit: 6c6c49f2c0993ab3ea4bb71a12c800afd0c59e30

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