linux-kernel - Re: [PATCH v2 0/2] enable flexspi support on imx8mp

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: <161669381898.42255.12902469942541515996.b4-ty@kernel.org>
Date:   Thu, 25 Mar 2021 17:37:01 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, Heiko Schocher <hs@...x.de>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        Ashish Kumar <ashish.kumar@....com>,
        Yogesh Gaur <yogeshgaur.83@...il.com>,
        devicetree@...r.kernel.org, Kuldeep Singh <kuldeep.singh@....com>,
        Shawn Guo <shawnguo@...nel.org>,
        linux-arm-kernel@...ts.infradead.org,
        Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH v2 0/2] enable flexspi support on imx8mp

On Tue, 16 Mar 2021 08:59:26 +0100, Heiko Schocher wrote:
> add compatible entry in nxp_fspi driver for imx8mp
> 
> @Shawn: If this series is accepted, can you apply the DTS patches from
> series v2?
> http://lists.infradead.org/pipermail/linux-arm-kernel/2021-March/643292.html
> http://lists.infradead.org/pipermail/linux-arm-kernel/2021-March/643293.html
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: fspi: enable fspi driver for on imx8mp
      commit: 0467a97367d4767d284ad46ba0e6413b621256a0
[2/2] dt-bindings: spi: add compatible entry for imx8mp in FlexSPI controller
      commit: 2801a62dfad46ff228d00126ce8592594c1d0613

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