From: Florian Fainelli <f.fainelli@gmail.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: anand.gore@broadcom.com, arnd@arndb.de,
bcm-kernel-feedback-list@broadcom.com, catalin.marinas@arm.com,
krzysztof.kozlowski@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, olof@lixom.net, soc@kernel.org,
will@kernel.org, william.zhang@broadcom.com,
anders.roxell@linaro.org, lkft@linaro.org
Subject: Re: arm64: Kconfig.platforms: Re-organized Broadcom menu
Date: Thu, 8 Sep 2022 09:43:33 -0700 [thread overview]
Message-ID: <588be35f-9293-0d26-1e89-5ba3a0f9bbc5@gmail.com> (raw)
In-Reply-To: <20220908110451.66564-1-naresh.kamboju@linaro.org>
On 9/8/2022 4:04 AM, Naresh Kamboju wrote:
> From: lkft@linaro.org
>
> LKFT test farm found that Linux next-20220906 onwards the Broadcom DTB
> builds are not happening. And after bisecting we found this patch is
> the reason [1].
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> FYI, We have not changed any kernel configs.
> [1] http://ix.io/49Wq
Fixed with:
https://lore.kernel.org/all/20220906033957.4377-1-f.fainelli@gmail.com/
sorry about the breakage and thanks for reporting!
--
Florian
prev parent reply other threads:[~2022-09-08 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 16:42 [PATCH] arm64: Kconfig.platforms: Re-organized Broadcom menu Florian Fainelli
2022-07-13 8:25 ` Arnd Bergmann
2022-07-13 8:40 ` Krzysztof Kozlowski
2022-07-13 9:17 ` Geert Uytterhoeven
2022-07-13 22:05 ` Florian Fainelli
2022-08-15 17:15 ` Florian Fainelli
2022-08-15 19:52 ` Arnd Bergmann
2022-09-08 11:04 ` Naresh Kamboju
2022-09-08 16:43 ` Florian Fainelli [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=588be35f-9293-0d26-1e89-5ba3a0f9bbc5@gmail.com \
--to=f.fainelli@gmail.com \
--cc=anand.gore@broadcom.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=will@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