linux-kernel - Re: [PATCH v2] dt-bindings: spi: zynqmp-qspi: Add power-domains and iommus properties

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: <168355243037.260152.6627127053306597242.b4-ty@kernel.org>
Date:   Mon, 08 May 2023 22:27:10 +0900
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, monstr@...str.eu, git@...inx.com,
        Michal Simek <michal.simek@....com>,
        Michal Simek <michal.simek@....com>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH v2] dt-bindings: spi: zynqmp-qspi: Add power-domains
 and iommus properties

On Wed, 03 May 2023 10:20:36 +0200, Michal Simek wrote:
> ZynqMP QSPI IP core has own power domain and also iommu ID that's why
> describe optional power-domains and iommus properties.
> 
> 

Applied to

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

Thanks!

[1/1] dt-bindings: spi: zynqmp-qspi: Add power-domains and iommus properties
      commit: 47e0255989560fbfd6cd0e03407982f37fdabe5a

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