From: kbuild test robot <fengguang.wu@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: [vfs:asm-exports 1/8] arch/avr32/lib/built-in.o: warning: input is not relaxable
Date: Sat, 16 Jan 2016 04:48:53 +0800 [thread overview]
Message-ID: <201601160451.RTseDQbE%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git asm-exports
head: 7edee3610000e590052ed9c4e1c97ed0c491e776
commit: 22319e98abd25dc2039b255def816bdef461c40a [1/8] [kbuild] handle exports in lib-y objects reliably
config: avr32-atngw100_defconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 22319e98abd25dc2039b255def816bdef461c40a
# save the attached .config to linux build tree
make.cross ARCH=avr32
All warnings (new ones prefixed by >>):
>> arch/avr32/lib/built-in.o: warning: input is not relaxable
virt/built-in.o: warning: input is not relaxable
>> arch/avr32/lib/built-in.o: warning: input is not relaxable
virt/built-in.o: warning: input is not relaxable
>> arch/avr32/lib/built-in.o: warning: input is not relaxable
virt/built-in.o: warning: input is not relaxable
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 11915 bytes --]
next reply other threads:[~2016-01-15 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 20:48 kbuild test robot [this message]
2016-01-15 22:59 ` [vfs:asm-exports 1/8] arch/avr32/lib/built-in.o: warning: input is not relaxable Al Viro
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=201601160451.RTseDQbE%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).