From: Florian Fainelli <f.fainelli@gmail.com>
To: William Zhang <william.zhang@broadcom.com>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>
Cc: anand.gore@broadcom.com, dan.beygelman@broadcom.com,
kursad.oney@broadcom.com, joel.peshkin@broadcom.com,
f.fainelli@gmail.com, Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [RESEND PATCH 7/8] spi: bcm63xx-hsspi: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA
Date: Thu, 7 Jul 2022 09:25:47 -0700 [thread overview]
Message-ID: <0b5fef8c-b42f-ad42-03e1-e50fe286ed9d@gmail.com> (raw)
In-Reply-To: <20220707065800.261269-7-william.zhang@broadcom.com>
On 7/6/22 23:57, William Zhang wrote:
> Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make
> SPI_BCM63XX_HSSPI depending on ARCH_BCMBCA.
>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
There is no cover letter for this 8 patch series :/ it is not clear to
me whether each subsystem maintainer will be in a position to merge
these patches individually, yet still have all 8 (7 of them actually,
see comment to patch 1) land in 5.20.
Alternatively, we can merge these patches through the Broadcom ARM SoC
pull request(s) to ensure they all land at the same time.
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: William Zhang <william.zhang@broadcom.com>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>
Cc: anand.gore@broadcom.com, dan.beygelman@broadcom.com,
kursad.oney@broadcom.com, joel.peshkin@broadcom.com,
f.fainelli@gmail.com, Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [RESEND PATCH 7/8] spi: bcm63xx-hsspi: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA
Date: Thu, 7 Jul 2022 09:25:47 -0700 [thread overview]
Message-ID: <0b5fef8c-b42f-ad42-03e1-e50fe286ed9d@gmail.com> (raw)
In-Reply-To: <20220707065800.261269-7-william.zhang@broadcom.com>
On 7/6/22 23:57, William Zhang wrote:
> Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make
> SPI_BCM63XX_HSSPI depending on ARCH_BCMBCA.
>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
There is no cover letter for this 8 patch series :/ it is not clear to
me whether each subsystem maintainer will be in a position to merge
these patches individually, yet still have all 8 (7 of them actually,
see comment to patch 1) land in 5.20.
Alternatively, we can merge these patches through the Broadcom ARM SoC
pull request(s) to ensure they all land at the same time.
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-07 16:25 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 6:57 [RESEND PATCH 1/8] ARM: debug: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA William Zhang
2022-07-07 6:57 ` William Zhang
2022-07-07 6:57 ` [RESEND PATCH 2/8] ata: ahci_brcm: " William Zhang
2022-07-07 6:57 ` William Zhang
2022-07-07 16:25 ` Florian Fainelli
2022-07-07 16:25 ` Florian Fainelli
2022-07-08 21:09 ` Florian Fainelli
2022-07-08 21:09 ` Florian Fainelli
2022-07-07 6:57 ` [RESEND PATCH 3/8] hwrng: bcm2835: " William Zhang
2022-07-07 6:57 ` William Zhang
2022-07-07 16:23 ` Florian Fainelli
2022-07-07 16:23 ` Florian Fainelli
2022-07-07 17:05 ` William Zhang
2022-07-07 17:05 ` William Zhang
2022-07-07 17:16 ` Conor.Dooley
2022-07-07 17:16 ` Conor.Dooley
2022-07-07 18:18 ` William Zhang
2022-07-07 18:18 ` William Zhang
2022-07-08 3:49 ` Florian Fainelli
2022-07-08 3:49 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-07 6:57 ` [RESEND PATCH 4/8] clk: bcm: " William Zhang
2022-07-07 6:57 ` William Zhang
2022-07-07 16:23 ` Florian Fainelli
2022-07-07 16:23 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-30 1:03 ` Stephen Boyd
2022-07-30 1:03 ` Stephen Boyd
2022-07-07 6:57 ` [RESEND PATCH 5/8] i2c: brcmstb: " William Zhang
2022-07-07 6:57 ` William Zhang
2022-07-07 16:24 ` Florian Fainelli
2022-07-07 16:24 ` Florian Fainelli
2022-07-07 20:52 ` Wolfram Sang
2022-07-07 20:52 ` Wolfram Sang
2022-07-08 21:09 ` Florian Fainelli
2022-07-08 21:09 ` Florian Fainelli
2022-07-07 6:57 ` [RESEND PATCH 6/8] phy: brcm-sata: " William Zhang
2022-07-07 6:57 ` William Zhang
2022-07-07 6:57 ` William Zhang
2022-07-07 16:25 ` Florian Fainelli
2022-07-07 16:25 ` Florian Fainelli
2022-07-07 16:25 ` Florian Fainelli
2022-07-08 21:10 ` Florian Fainelli
2022-07-08 21:10 ` Florian Fainelli
2022-07-08 21:10 ` Florian Fainelli
2022-07-07 6:57 ` [RESEND PATCH 7/8] spi: bcm63xx-hsspi: " William Zhang
2022-07-07 6:57 ` William Zhang
2022-07-07 16:25 ` Florian Fainelli [this message]
2022-07-07 16:25 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-11 10:45 ` Mark Brown
2022-07-11 10:45 ` Mark Brown
2022-07-11 16:04 ` Florian Fainelli
2022-07-11 16:04 ` Florian Fainelli
2022-07-11 16:09 ` Mark Brown
2022-07-11 16:09 ` Mark Brown
2022-07-13 16:11 ` Florian Fainelli
2022-07-13 16:11 ` Florian Fainelli
2022-07-07 6:57 ` [RESEND PATCH 8/8] tty: serial: bcm63xx: " William Zhang
2022-07-07 6:57 ` William Zhang
2022-07-07 16:26 ` Florian Fainelli
2022-07-07 16:26 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-07 16:22 ` [RESEND PATCH 1/8] ARM: debug: " Florian Fainelli
2022-07-07 16:22 ` Florian Fainelli
2022-07-08 21:08 ` Florian Fainelli
2022-07-08 21:08 ` Florian Fainelli
2022-07-13 15:39 ` Rafał Miłecki
2022-07-13 15:39 ` Rafał Miłecki
2022-07-13 16:10 ` Florian Fainelli
2022-07-13 16:10 ` Florian Fainelli
2022-07-13 20:19 ` Rafał Miłecki
2022-07-13 20:19 ` Rafał Miłecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b5fef8c-b42f-ad42-03e1-e50fe286ed9d@gmail.com \
--to=f.fainelli@gmail.com \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=dan.beygelman@broadcom.com \
--cc=joel.peshkin@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=william.zhang@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.