From: Miaohe Lin <linmiaohe@huawei.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: kernel test robot <lkp@intel.com>, <llvm@lists.linux.dev>,
<oe-kbuild-all@lists.linux.dev>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Mike Rapoport (IBM)" <rppt@kernel.org>
Subject: Re: [linux-next:master 7083/7933] ld.lld: error: assignment to symbol __init_end does not converge
Date: Fri, 11 Aug 2023 11:21:45 +0800 [thread overview]
Message-ID: <91e55036-3d7d-7de4-a9ca-002081cdbcea@huawei.com> (raw)
In-Reply-To: <20230811030049.GA3949452@dev-arch.thelio-3990X>
On 2023/8/11 11:00, Nathan Chancellor wrote:
> On Fri, Aug 11, 2023 at 09:58:02AM +0800, Miaohe Lin wrote:
>> On 2023/8/9 3:26, kernel test robot wrote:
>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>>> head: 71cd4fc492ec41e4acd85e98bbf7a13753fc1e03
>>> commit: 489dcf298fbc8c0be81d98a6477ddeadc7327858 [7083/7933] mm/mm_init.c: remove obsolete macro HASH_SMALL
>>> config: arm64-randconfig-r032-20230808 (https://download.01.org/0day-ci/archive/20230809/202308090338.AqDF9eEK-lkp@intel.com/config)
>>> compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
>>> reproduce: (https://download.01.org/0day-ci/archive/20230809/202308090338.AqDF9eEK-lkp@intel.com/reproduce)
>>>
>>> If you fix the issue in a separate patch/commit (i.e. not just a new version of
>>> the same patch/commit), kindly add following tags
>>> | Reported-by: kernel test robot <lkp@intel.com>
>>> | Closes: https://lore.kernel.org/oe-kbuild-all/202308090338.AqDF9eEK-lkp@intel.com/
>>>
>>> Note: the linux-next/master HEAD 71cd4fc492ec41e4acd85e98bbf7a13753fc1e03 builds fine.
>>> It may have been fixed somewhere.
>>>
>>> All errors (new ones prefixed by >>):
>>>
>>>>> ld.lld: error: assignment to symbol __init_end does not converge
>>
>> Thanks for your report. It seems that commit is irrelevant to the problem and I have no idea what
>> this error means. Could you please give me some more information?
>
> This is a known randconfig failure, it is safe for you to ignore it.
Many thanks for your information! This really helps. :)
>
> https://github.com/ClangBuiltLinux/linux/issues/1790
>
> Cheers,
> Nathan
> .
>
prev parent reply other threads:[~2023-08-11 3:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 19:26 kernel test robot
2023-08-11 1:58 ` Miaohe Lin
2023-08-11 3:00 ` Nathan Chancellor
2023-08-11 3:21 ` Miaohe Lin [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=91e55036-3d7d-7de4-a9ca-002081cdbcea@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rppt@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