linux-kernel - Re: (subset) [PATCH v3 0/4] fix the flexspi error on imx8ulp

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <172557369118.138179.1237587939116968087.b4-ty@kernel.org>
Date: Thu, 05 Sep 2024 23:01:31 +0100
From: Mark Brown <broonie@...nel.org>
To: han.xu@....com, yogeshgaur.83@...il.com, robh@...nel.org, 
 krzk+dt@...nel.org, conor+dt@...nel.org, shawnguo@...nel.org, 
 s.hauer@...gutronix.de, haibo.chen@....com
Cc: kernel@...gutronix.de, festevam@...il.com, singh.kuldeep87k@...il.com, 
 hs@...x.de, linux-spi@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-kernel@...r.kernel.org, imx@...ts.linux.dev, 
 linux-arm-kernel@...ts.infradead.org, peng.fan@....com, stable@...nel.org
Subject: Re: (subset) [PATCH v3 0/4] fix the flexspi error on imx8ulp

On Thu, 05 Sep 2024 17:43:34 +0800, haibo.chen@....com wrote:
> The flexspi on imx8ulp only has 16 LUTs, different with others
> which has 32 LUTs. So currently flexspi driver will write the
> wrong register when fill LUT.
> 
> This patch set add a new compatible string for imx8ulp to
> distinguish the LUT number.
> 
> [...]

Applied to

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

Thanks!

[1/4] dt-bindings: spi: nxp-fspi: add imx8ulp support
      commit: 12736adc43b7cd5cb83f274f8f37b0f89d107c97
[2/4] spi: fspi: involve lut_num for struct nxp_fspi_devtype_data
      commit: 190b7e2efb1ed8435fc7431d9c7a2447d05d5066
[3/4] spi: fspi: add support for imx8ulp
      commit: 9228956a620553d7fd17f703a37a26c91e4d92ab

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