linux-kernel - Re: [PATCH v2] spi: imx: add i.MX51 ECSPI target mode support

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: <176250806608.2489052.17181780089794986836.b4-ty@kernel.org>
Date: Fri, 07 Nov 2025 09:34:26 +0000
From: Mark Brown <broonie@...nel.org>
To: mkl@...gutronix.de, frank.li@....com, shawnguo@...nel.org, 
 s.hauer@...gutronix.de, kernel@...gutronix.de, festevam@...il.com, 
 carlos.song@....com
Cc: linux-spi@...r.kernel.org, imx@...ts.linux.dev, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] spi: imx: add i.MX51 ECSPI target mode support

On Mon, 27 Oct 2025 19:02:56 +0800, carlos.song@....com wrote:
> ECSPI in i.MX51 and i.MX53 support target mode. Current code only support
> i.MX53. Remove is_imx53_ecspi() check for target mode to support i.MX51.
> 
> 

Applied to

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

Thanks!

[1/1] spi: imx: add i.MX51 ECSPI target mode support
      commit: 4e92abd0a11b91af3742197a9ca962c3c00d0948

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