linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	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: dan.beygelman@broadcom.com, anand.gore@broadcom.com,
	joel.peshkin@broadcom.com, Arnd Bergmann <arnd@arndb.de>,
	kursad.oney@broadcom.com, linux-kernel@vger.kernel.org,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Russell King <linux@armlinux.org.uk>,
	Nathan Chancellor <nathan@kernel.org>,
	Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Eugen Hristev <eugen.hristev@microchip.com>,
	Shawn Guo <shawnguo@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [RESEND PATCH 1/8] ARM: debug: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA
Date: Wed, 13 Jul 2022 22:19:14 +0200	[thread overview]
Message-ID: <fced7f47-985b-7ef8-431b-051353a56d30@gmail.com> (raw)
In-Reply-To: <5392c58e-d479-94c9-f025-099f99ae17ba@gmail.com>

On 13.07.2022 18:10, Florian Fainelli wrote:
> On 7/13/22 08:39, Rafał Miłecki wrote:
>> On 7.07.2022 08:57, William Zhang wrote:
>>> Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make
>>> DEBUG_BCM63XX_UART depending on ARCH_BCMBCA.
>>>
>>> Signed-off-by: William Zhang <william.zhang@broadcom.com>
>>> ---
>>>
>>>   arch/arm/Kconfig.debug | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
>>> index 9b0aa4822d69..792796a348c3 100644
>>> --- a/arch/arm/Kconfig.debug
>>> +++ b/arch/arm/Kconfig.debug
>>> @@ -271,7 +271,7 @@ choice
>>>       config DEBUG_BCM63XX_UART
>>>           bool "Kernel low-level debugging on BCM63XX UART"
>>> -        depends on ARCH_BCM_63XX
>>> +        depends on ARCH_BCMBCA
>>>       config DEBUG_BERLIN_UART
>>>           bool "Marvell Berlin SoC Debug UART"
>>
>> There is no such config symbol (ARCH_BCMBCA) in Linus's tree.
>>
>> This patchset is going to break builds until code it depends on hits Linus's tree.
>>
>> All those patches should be hold until that.
> 
> There is, ARCH_BCMBCA was added to arch/arm/mach-bcm/Kconfig with b32c613b3fda3 ("arm: bcmbca: add arch bcmbca machine entry") which is in v5.19-rc1 and newer:

Oops, my tree updating script failed me. Sorry!

OK then, maybe this migration wasn't handled flawlessly but it's half
done now and remaining things should be fixed with all pending work.
Looks OK!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-07-13 20:20 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
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 [this message]

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=fced7f47-985b-7ef8-431b-051353a56d30@gmail.com \
    --to=zajec5@gmail.com \
    --cc=anand.gore@broadcom.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dan.beygelman@broadcom.com \
    --cc=eugen.hristev@microchip.com \
    --cc=f.fainelli@gmail.com \
    --cc=joel.peshkin@broadcom.com \
    --cc=kavyasree.kotagiri@microchip.com \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lukas.bulwahn@gmail.com \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=shawnguo@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 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).