linux-kernel - Re: [Patch v2 0/4] NXP Flexspi driver patches

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]

Date:   Thu, 04 Mar 2021 00:56:28 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Kuldeep Singh <kuldeep.singh@....com>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org
Cc:     Rob Herring <robh+dt@...nel.org>,
        Ashish Kumar <ashish.kumar@....com>
Subject: Re: [Patch v2 0/4] NXP Flexspi driver patches

On Tue, 2 Mar 2021 18:19:32 +0530, Kuldeep Singh wrote:
> This patchset involves changes in NXP Flexspi driver.
> 
> Patch1 adds support for disabling AHB and enabling IP read only using a
> quirk which is later used by patch3 and patch4.
> 
> Patch3 and Patch4 are not related to each and are rather dependent on
> patch1 and that's why I kept them in series. This also helps in easy
> application of series.
> 
> [...]

Applied to

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

Thanks!

[1/4] spi: spi-nxp-fspi: Add support for IP read only
      commit: 1e1c30db2ccba3ec891e683f5e8eca2aca6238eb
[2/4] dt-bindings: spi: spi-nxp-fspi: Add imx8dxl support
      commit: a53a9159a6774b393bb4b620430328940fa853b8
[3/4] spi: spi-nxp-fspi: Add imx8dxl driver support
      commit: 99a6a399a61e95cd6639453f87d5c96a121dec07
[4/4] spi: spi-nxp-fspi: Implement errata workaround for LS1028A
      commit: 94f302f374b4544fa4d84526569f884ebb008f4d

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