From: Stephen Boyd <sboyd@kernel.org>
To: Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>,
William Zhang <william.zhang@broadcom.com>
Cc: anand.gore@broadcom.com, dan.beygelman@broadcom.com,
kursad.oney@broadcom.com, joel.peshkin@broadcom.com,
f.fainelli@gmail.com, William Zhang <william.zhang@broadcom.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 4/8] clk: bcm: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA
Date: Fri, 29 Jul 2022 18:03:49 -0700 [thread overview]
Message-ID: <20220730010351.AF9ACC433C1@smtp.kernel.org> (raw)
In-Reply-To: <20220707065800.261269-4-william.zhang@broadcom.com>
Quoting William Zhang (2022-07-06 23:57:55)
> Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make
> CLK_BCM_63XX depending and setting default on ARCH_BCMBCA.
>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
_______________________________________________
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-30 1:04 UTC|newest]
Thread overview: 37+ 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 ` [RESEND PATCH 2/8] ata: ahci_brcm: " William Zhang
2022-07-07 16:25 ` 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 16:23 ` Florian Fainelli
2022-07-07 17:05 ` William Zhang
2022-07-07 17:16 ` Conor.Dooley
2022-07-07 18:18 ` William Zhang
2022-07-08 3:49 ` 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 16:23 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-30 1:03 ` Stephen Boyd [this message]
2022-07-07 6:57 ` [RESEND PATCH 5/8] i2c: brcmstb: " William Zhang
2022-07-07 16:24 ` Florian Fainelli
2022-07-07 20:52 ` Wolfram Sang
2022-07-08 21:09 ` Florian Fainelli
2022-07-07 6:57 ` [RESEND PATCH 6/8] phy: brcm-sata: " William Zhang
2022-07-07 16:25 ` 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 16:25 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-11 10:45 ` Mark Brown
2022-07-11 16:04 ` Florian Fainelli
2022-07-11 16:09 ` Mark Brown
2022-07-13 16:11 ` Florian Fainelli
2022-07-07 6:57 ` [RESEND PATCH 8/8] tty: serial: bcm63xx: " William Zhang
2022-07-07 16:26 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
2022-07-07 16:22 ` [RESEND PATCH 1/8] ARM: debug: " Florian Fainelli
2022-07-08 21:08 ` Florian Fainelli
2022-07-13 15:39 ` Rafał Miłecki
2022-07-13 16:10 ` Florian Fainelli
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=20220730010351.AF9ACC433C1@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.beygelman@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=joel.peshkin@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).