linux-kernel - Re: [PATCH v2] dt-bindings: spi: convert Cadence SPI bindings to YAML

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: <162394121400.19455.13291098800034403183.b4-ty@kernel.org>
Date:   Thu, 17 Jun 2021 16:01:13 +0100
From:   Mark Brown <broonie@...nel.org>
To:     michal.simek@...inx.com, robh+dt@...nel.org,
        Nobuhiro Iwamatsu <iwamatsu@...auri.org>
Cc:     Mark Brown <broonie@...nel.org>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        harinik@...inx.com, devicetree@...r.kernel.org,
        linux-spi@...r.kernel.org
Subject: Re: [PATCH v2] dt-bindings: spi: convert Cadence SPI bindings to YAML

On Sat, 5 Jun 2021 09:38:11 +0900, Nobuhiro Iwamatsu wrote:
> Convert spi for Cadence SPI bindings documentation to YAML.

Applied to

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

Thanks!

[1/1] dt-bindings: spi: convert Cadence SPI bindings to YAML
      commit: aa7968682a2b8a9cecf1d7d07e1c8ae8c08d211e

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