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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat,  2 Oct 2021 02:37:05 +0100
From:   Mark Brown <>
To:     Michael Walle <>,,
Cc:     Mark Brown <>,
        Vladimir Oltean <>,
        Yogesh Gaur <>,
        Kuldeep Singh <>,
        Ashish Kumar <>
Subject: Re: [PATCH] spi: spi-nxp-fspi: don't depend on a specific node name erratum workaround

On Fri, 1 Oct 2021 23:27:26 +0200, Michael Walle wrote:
> In commit 7e71b85473f8 ("arm64: dts: ls1028a: fix node name for the
> sysclk") the sysclk node name was renamed and broke the erratum
> workaround because it tries to fetch a device tree node by its name,
> which is very fragile in general. We don't even need the sysclk node
> because the only possible sysclk frequency input is 100MHz. In fact, the
> erratum says it applies if SYS_PLL_RAT is 3, not that the platform clock
> is 300 MHz. Make the workaround more reliable and just drop the unneeded
> sysclk lookup.
> [...]

Applied to for-next


[1/1] spi: spi-nxp-fspi: don't depend on a specific node name erratum workaround
      commit: 67a12ae52599c9f2f24ef14adb43fc3b164792b5

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.


Powered by blists - more mailing lists