linux-kernel - Re: (subset) [PATCH V1 0/2] Add device tree compatible for sc7180 SoC

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <163313862169.2275998.5804867182938981158.b4-ty@kernel.org>
Date:   Sat,  2 Oct 2021 02:37:06 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        Doug Anderson <dianders@...omium.org>,
        Rob Herring <robh+dt@...nel.org>,
        Rajesh Patil <rajpat@...eaurora.org>,
        Andy Gross <agross@...nel.org>
Cc:     Mark Brown <broonie@...nel.org>, linux-arm-msm@...r.kernel.org,
        devicetree@...r.kernel.org, saiprakash.ranjan@...eaurora.org,
        linux-kernel@...r.kernel.org, rnayak@...eaurora.org,
        mka@...omium.org, msavaliy@....qualcomm.com, sboyd@...nel.org,
        skakit@...eaurora.org
Subject: Re: (subset) [PATCH V1 0/2] Add device tree compatible for sc7180 SoC

On Thu, 30 Sep 2021 15:54:08 +0530, Rajesh Patil wrote:
>  - As per Doug's comments
>    1. Added device tree compatible in dt-bindings
>    2. Added "qcom,sc718-qspi" in qspi node
> 
> Rajesh Patil (2):
>   dt-bindings: spi: Add sc7180 support
>   arm64: dts: qcom: sc7180: Add qspi compatible
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: spi: Add sc7180 support
      commit: acde408188491ab8965c10bf82bb06600599cdd4

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