From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>, f.fainelli@gmail.com
Cc: andersson@kernel.org, arnd@arndb.de, biju.das.jz@bp.renesas.com,
catalin.marinas@arm.com, dmitry.baryshkov@linaro.org,
geert+renesas@glider.be, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, marcel.ziswiler@toradex.com,
michael@walle.cc, shawnguo@kernel.org, soc@kernel.org,
vkoul@kernel.org, will@kernel.org, lkft-triage@lists.linaro.org,
Linux Kernel Functional Testing <lkft@linaro.org>
Subject: Re: [PATCH] arm64: defconfig: enable ARCH_BCM
Date: Fri, 9 Sep 2022 09:38:22 +0200 [thread overview]
Message-ID: <51e6ea21-8af4-775d-1561-6671cfc50ecf@linaro.org> (raw)
In-Reply-To: <20220909073509.301363-1-naresh.kamboju@linaro.org>
On 09/09/2022 09:35, Naresh Kamboju wrote:
> From: Naresh kamboju <naresh.kamboju@linaro.org>
>
>
> On 2022-09-05 20:39, Florian Fainelli wrote:
>> Commit 96796c914b84 ("arm64: Kconfig.platforms: Re-organized Broadcom
>> menu") introduced a new symbol ARCH_BCM and made all of the Broadcom
>> SoCs Kconfig depend on it, but did not enable it in the defconfig.
>> Thus, now the defconfig doesn't include support for any Broadcom
>> architectures anymore. Fix it.
>>
>> Fixes: 96796c914b84 ("arm64: Kconfig.platforms: Re-organized Broadcom menu")
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
The patch was sent on 6th of September. Your report on 8th of September...
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-09 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 3:39 Florian Fainelli
2022-09-08 18:17 ` Anders Roxell
2022-09-09 7:35 ` Naresh Kamboju
2022-09-09 7:38 ` Krzysztof Kozlowski [this message]
2022-09-09 12:24 ` Naresh Kamboju
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=51e6ea21-8af4-775d-1561-6671cfc50ecf@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=biju.das.jz@bp.renesas.com \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lkft@linaro.org \
--cc=marcel.ziswiler@toradex.com \
--cc=michael@walle.cc \
--cc=naresh.kamboju@linaro.org \
--cc=shawnguo@kernel.org \
--cc=soc@kernel.org \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®