From: kbuild test robot <lkp@intel.com>
To: zhangaihua1@huawei.com
Cc: kbuild-all@01.org, tytso@mit.edu, linux-ext4@vger.kernel.org,
zhangaihua <zhangaihua1@huawei.com>
Subject: Re: [PATCH] fix waring calltrace when usb was ejected.
Date: Wed, 24 Feb 2016 13:51:29 +0800 [thread overview]
Message-ID: <201602241345.0ejtdtH2%fengguang.wu@intel.com> (raw)
In-Reply-To: <1456287921-8961-1-git-send-email-zhangaihua1@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Hi zhangaihua,
[auto build test ERROR on ext4/dev]
[also build test ERROR on v4.5-rc5 next-20160223]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/zhangaihua1-huawei-com/fix-waring-calltrace-when-usb-was-ejected/20160224-122520
base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
config: arm-allnoconfig (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
# save the attached .config to linux build tree
make.cross ARCH=arm
All errors (new ones prefixed by >>):
fs/built-in.o: In function `__mark_inode_dirty':
>> :(.text+0x14ac2): undefined reference to `block_device_ejected'
---
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: 5459 bytes --]
prev parent reply other threads:[~2016-02-24 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 4:25 [PATCH] fix waring calltrace when usb was ejected zhangaihua1
2016-02-24 4:44 ` kbuild test robot
2016-02-24 5:04 ` kbuild test robot
2016-02-24 5:51 ` kbuild test robot [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=201602241345.0ejtdtH2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=zhangaihua1@huawei.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;
as well as URLs for NNTP newsgroup(s).