From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, slade@sladewatkins.com
Subject: Re: [PATCH 5.17 0000/1123] 5.17.2-rc2 review
Date: Fri, 8 Apr 2022 15:07:50 +0700 [thread overview]
Message-ID: <374de447-0d28-6b85-6abc-687d9a444b66@gmail.com> (raw)
In-Reply-To: <d12e1f2e-bcad-e7d5-5d14-e435340ffc2c@gmail.com>
On 07/04/22 18.45, Bagas Sanjaya wrote:
> Successfully cross-compiled for arm64 (bcm2711_defconfig, gcc 10.2.0).
>
> Tested-by: Bagas Sanjaya <bagasdotme@gmail.com>
>
> powerpc build (ps3_defconfig, gcc 11.2.0) returned error:
>
> CC [M] arch/powerpc/kvm/book3s_hv.o
> CC kernel/kexec_file.o
> Cannot find symbol for section 11: .text.unlikely.
> kernel/kexec_file.o: failed
> make[1]: *** [scripts/Makefile.build:288: kernel/kexec_file.o] Error 1
> make[1]: *** Deleting file 'kernel/kexec_file.o'
> make: *** [Makefile:1831: kernel] Error 2
>
> Reported-by: Bagas Sanjaya <bagasdotme@gmail.com>
>
Oops, I didn't do make mrproper before powerpc build.
Now the powerpc build runs successfully.
Tested-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-08 8:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 13:44 Greg Kroah-Hartman
2022-04-06 19:23 ` Justin Forbes
2022-04-06 19:58 ` Fox Chen
2022-04-06 22:48 ` Shuah Khan
2022-04-06 23:52 ` Florian Fainelli
2022-04-07 0:37 ` Ron Economos
2022-04-07 8:35 ` Jiri Slaby
2022-04-07 10:57 ` Naresh Kamboju
2022-04-07 11:45 ` Bagas Sanjaya
2022-04-08 8:07 ` Bagas Sanjaya [this message]
2022-04-11 14:53 ` Geert Uytterhoeven
2022-04-07 17:44 ` Guenter Roeck
2022-04-07 22:11 ` Sebastian Döring
2022-04-07 23:02 ` Rudi Heitbaum
2022-04-06 22:52 Ronald Warsow
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=374de447-0d28-6b85-6abc-687d9a444b66@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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®