linux-kernel - Re: [RESEND PATCH 7/8] spi: bcm63xx-hsspi: bcmbca: Replace ARCH_BCM_63XX with ARCH

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: <ce3f1df4-6919-e666-a8d0-a856e5d7bc3b@gmail.com>
Date:   Mon, 11 Jul 2022 09:04:39 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Mark Brown <broonie@...nel.org>,
        Florian Fainelli <f.fainelli@...il.com>
Cc:     bcm-kernel-feedback-list@...adcom.com,
        William Zhang <william.zhang@...adcom.com>,
        Linux ARM List <linux-arm-kernel@...ts.infradead.org>,
        anand.gore@...adcom.com, dan.beygelman@...adcom.com,
        kursad.oney@...adcom.com, joel.peshkin@...adcom.com,
        linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [RESEND PATCH 7/8] spi: bcm63xx-hsspi: bcmbca: Replace
 ARCH_BCM_63XX with ARCH_BCMBCA

On 7/11/22 03:45, Mark Brown wrote:
> On Sun, Jul 10, 2022 at 07:11:31PM -0700, Florian Fainelli wrote:
>> On Wed,  6 Jul 2022 23:57:58 -0700, William Zhang <william.zhang@...adcom.com> wrote:
>>> Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make
>>> SPI_BCM63XX_HSSPI depending on ARCH_BCMBCA.
> 
>> Applied to https://github.com/Broadcom/stblinux/commits/drivers/next, thanks!
> 
> I was rather hoping for an answer on what the situation with
> dependencies was here...

Each patch is independent from one another and there are not 
dependencies on the Broadcom arm-soc tree(s) other than for 
CONFIG_ARCH_BCMBCA which was introduced with v5.19 with 
b32c613b3fda3e1c26119609f1ad6b19178f82f5. That said, I prefer to take 
all patches via the Broadcom arm-soc tree(s) to ensure a timely 
inclusion for our upcoming v5.20 pull request, and ensure that all 
drivers are converted in one release cycle.

If you want to give me your Acked-by or that I drop this and take it via 
the spi tree, please let me know.

Thanks!
-- 
Florian