From: Eric Biggers <ebiggers@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-kernel@vger.kernel.or, lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
"David S. Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: next-20250507: arm64 local label `"3" (instance number 1 of a fb label)' is not defined
Date: Wed, 7 May 2025 10:30:31 -0700 [thread overview]
Message-ID: <20250507173031.GC181648@sol> (raw)
In-Reply-To: <CA+G9fYvcXTuxC0ncXBQYh8FZE2BxGSuTi6dvN_sWxBRcOAN8tQ@mail.gmail.com>
On Wed, May 07, 2025 at 10:58:18PM +0530, Naresh Kamboju wrote:
> Regressions on arm64 lkftconfig failed with gcc-12 on the Linux next-20250507.
>
> First seen on the next-20250507
> Good: next-20250506
> Bad: next-20250507
>
> Regressions found on arm64:
> - build/gcc-12-lkftconfig-graviton4
>
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? Yes
>
> Build regression: arm64 local label `"3" (instance number 1 of a fb
> label)' is not defined
Fix was already sent:
https://lore.kernel.org/linux-crypto/20250507170901.151548-1-ebiggers@kernel.org
- Eric
prev parent reply other threads:[~2025-05-07 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 17:28 next-20250507: arm64 local label `"3" (instance number 1 of a fb label)' is not defined Naresh Kamboju
2025-05-07 17:30 ` Eric Biggers [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=20250507173031.GC181648@sol \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.or \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--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