From: Luis Chamberlain <mcgrof@kernel.org>
To: kernel test robot <lkp@intel.com>,
tsbogend@alpha.franken.de, linux-mips@vger.kernel.org
Cc: Aaron Tomlin <atomlin@redhat.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [linux-next:master 1238/7959] mips64el-linux-ld: warning: orphan section `.ctors.65436' from `kernel/module/main.o' being placed in section `.ctors.65436'
Date: Mon, 9 May 2022 15:34:34 -0700 [thread overview]
Message-ID: <YnmW+il1s2TKKh13@bombadil.infradead.org> (raw)
In-Reply-To: <202205022005.yeXAj5Zz-lkp@intel.com>
On Mon, May 02, 2022 at 08:06:59PM +0800, kernel test robot wrote:
> All warnings (new ones prefixed by >>):
>
> mips64el-linux-ld: warning: orphan section `.ctors.65436' from `arch/mips/kernel/signal_o32.o' being placed in section `.ctors.65436'
<-- tons of these -->
<-- snip -->
> >> mips64el-linux-ld: warning: orphan section `.ctors.65436' from `kernel/module/main.o' being placed in section `.ctors.65436'
This is not due to the changes, this is just that the linker for
mips64el-linux-ld loves to complain about these for any new kernel
object.
So nothing will be done or can be done as far as modules-next is
concerned.
Luis
next parent reply other threads:[~2022-05-09 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202205022005.yeXAj5Zz-lkp@intel.com>
2022-05-09 22:34 ` Luis Chamberlain [this message]
2022-05-12 9:38 ` [kbuild-all] Re: [linux-next:master 1238/7959] mips64el-linux-ld: warning: orphan section `.ctors.65436' from `kernel/module/main.o' being placed in section `.ctors.65436' Chen, Rong A
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=YnmW+il1s2TKKh13@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=atomlin@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=kbuild-all@lists.01.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=tsbogend@alpha.franken.de \
/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).