From: Catalin Marinas <catalin.marinas@arm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "kernelci.org bot" <bot@kernelci.org>,
will@kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io, Yuan Kang <Yuan.Kang@freescale.com>
Subject: Re: arm64/for-kernelci build: 2 builds: 1 failed, 1 passed, 1 error, 1 warning (v6.2-rc6-115-gca72d58361ee)
Date: Mon, 6 Feb 2023 13:23:03 +0000 [thread overview]
Message-ID: <Y+D/N7PaOwmhKWZn@arm.com> (raw)
In-Reply-To: <Y+DPHtF5E6KnAhCv@gondor.apana.org.au>
On Mon, Feb 06, 2023 at 05:57:50PM +0800, Herbert Xu wrote:
> On Fri, Feb 03, 2023 at 09:40:30PM +0000, Catalin Marinas wrote:
> > Actually, we can conclude that gcc-10 is not smart enough and ignore
> > this report. The call gen_split_key() has len == 0:
>
> Yes. In any case, this should already be fixed in linux-next with
>
> https://lore.kernel.org/lkml/f3e9add2210a46af99cf0fc79121c7db@AcuMS.aculab.com/T/
>
> Please let me know if the problem persists with this patch.
Thanks, good to know it's in -next. The patch above should clear the
error, I did something similar locally just to check.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-02-06 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 21:59 arm64/for-kernelci build: 2 builds: 1 failed, 1 passed, 1 error, 1 warning (v6.2-rc6-115-gca72d58361ee) kernelci.org bot
2023-02-03 18:26 ` Catalin Marinas
2023-02-03 21:40 ` Catalin Marinas
2023-02-06 9:57 ` Herbert Xu
2023-02-06 13:23 ` Catalin Marinas [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=Y+D/N7PaOwmhKWZn@arm.com \
--to=catalin.marinas@arm.com \
--cc=Yuan.Kang@freescale.com \
--cc=bot@kernelci.org \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).