linux-kernel - Re: [PATCH V3 0/3] Convert mxs/imx spi/cspi/lpspi binding to json-schema

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: <159439561193.49235.7694501887022961004.b4-ty@kernel.org>
Date:   Fri, 10 Jul 2020 16:40:11 +0100
From:   Mark Brown <broonie@...nel.org>
To:     s.hauer@...gutronix.de, kernel@...gutronix.de,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org, shawnguo@...nel.org, robh+dt@...nel.org,
        Anson Huang <Anson.Huang@....com>, marex@...x.de,
        devicetree@...r.kernel.org, festevam@...il.com
Cc:     Linux-imx@....com
Subject: Re: [PATCH V3 0/3] Convert mxs/imx spi/cspi/lpspi binding to json-schema

On Tue, 16 Jun 2020 12:26:12 +0800, Anson Huang wrote:
> This patch series converts mxs/imx spi/cspi/lpspi binding to json-schema.
> 
> In fsl-imx-cspi.yaml, also update compatible, remove obsolete properties
> "fsl,spi-num-chipselects" and update the example based on latest DT file;
> 
> In spi-fsl-lpspi.yaml, the original maintainer's email address pandy.gao@....com
> is no longer valid, so I use mine.
> 
> [...]

Applied to

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

Thanks!

[1/3] dt-bindings: spi: Convert mxs spi to json-schema
      commit: e013bf2d96528c382f232a6ee068990d63e81a3d
[2/3] dt-bindings: spi: Convert imx cspi to json-schema
      commit: 790739c4417c17b2201bc742a9d5d819ea71799f
[3/3] dt-bindings: spi: Convert imx lpspi to json-schema
      commit: be8faebc2e55b2e5a335b606d11d070d53e78133

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