From: kbuild test robot <lkp@intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 298/371] {standard input}:124: Warning: .ent or .aent not in text section
Date: Wed, 13 Feb 2019 23:32:53 +0800 [thread overview]
Message-ID: <201902132350.SmzoeQC1%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 9ee6a8c1599037fee13ab8a1780092b96db446df
commit: 2903b418aef5ba68068d3a9a6f8c8e6ff28f6485 [298/371] kernel/configs: use .incbin directive to embed config_data.gz
config: mips-allmodconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 8.2.0-11) 8.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 2903b418aef5ba68068d3a9a6f8c8e6ff28f6485
# save the attached .config to linux build tree
GCC_VERSION=8.2.0 make.cross ARCH=mips
All warnings (new ones prefixed by >>):
{standard input}: Assembler messages:
>> {standard input}:124: Warning: .ent or .aent not in text section
>> {standard input}:165: Warning: .end not in text section
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 58691 bytes --]
next reply other threads:[~2019-02-13 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 15:32 kbuild test robot [this message]
2019-02-14 1:25 ` yamada.masahiro
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=201902132350.SmzoeQC1%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=yamada.masahiro@socionext.com \
/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