linux-kernel - Re: [PATCH 1/4] dt-bindings: spi: Add compatible string for brcmstb SoCs

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: <a1e13626-e87a-8114-74ae-560902ab9551@gmail.com>
Date:   Wed, 23 Sep 2020 13:38:55 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Mark Brown <broonie@...nel.org>,
        Florian Fainelli <f.fainelli@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Kamal Dasu <kdasu.kdev@...il.com>,
        Ray Jui <ray.jui@...adcom.com>
Cc:     linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
        bcm-kernel-feedback-list@...adcom.com, devicetree@...r.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: spi: Add compatible string for brcmstb
 SoCs

On 9/14/20 7:52 AM, Mark Brown wrote:
> On Thu, 10 Sep 2020 08:25:36 -0700, Ray Jui wrote:
>> Add compatible string for brcmstb 7445 SoCs.
> 
> Applied to
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
> 
> Thanks!
> 
> [1/4] spi: Add compatible string for brcmstb SoCs
>       commit: d9f0cf9f1176d36d3824459d5b061f4719fcbb8a
> [2/4] spi: bcm-qspi: Add compatible string for BRCMSTB 7445 SoCs
>       commit: e0eeb76b818ad93718f9640b0bdad909b453a3b8
> [3/4] spi: bcm-qspi: Fix probe regression on iProc platforms
>       commit: 9a852d44b26f8e60e2ae13df563824c0f8489135
> [4/4] spi: bcm-qspi: Clean up 7425, 7429, and 7435 settings
>       commit: 3cf5d198785a6b454e6a97246795b0043aff9ac1
> 
> 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.

Mark, can you also submit "spi: bcm-qspi: Fix probe regression on iProc
platforms" towards Linus because this is a bug fix that is currently
affecting the 5.9 kernel.

Thanks
-- 
Florian