From: kbuild test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild-all@01.org, bfields@fieldses.org, chucklever@gmail.com,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: restore owner override for truncate
Date: Fri, 10 Feb 2017 07:56:57 +0800 [thread overview]
Message-ID: <201702100750.CPa0FiBP%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170209142238.5322-1-hch@lst.de>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Hi Christoph,
[auto build test ERROR on nfsd/nfsd-next]
[also build test ERROR on v4.10-rc7 next-20170209]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Christoph-Hellwig/nfsd-restore-owner-override-for-truncate/20170210-035117
base: git://linux-nfs.org/~bfields/linux.git nfsd-next
config: powerpc-mvme5100_defconfig (attached as .config)
compiler: powerpc-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
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=powerpc
All errors (new ones prefixed by >>):
>> ERROR: "do_truncate" [fs/nfsd/nfsd.ko] undefined!
---
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: 13033 bytes --]
prev parent reply other threads:[~2017-02-09 23:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 14:22 [PATCH] nfsd: restore owner override for truncate Christoph Hellwig
2017-02-09 15:56 ` Chuck Lever
2017-02-09 16:01 ` J. Bruce Fields
2017-02-09 16:01 ` Christoph Hellwig
2017-02-09 18:04 ` Chuck Lever
2017-02-09 19:32 ` J. Bruce Fields
2017-02-09 23:56 ` 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=201702100750.CPa0FiBP%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bfields@fieldses.org \
--cc=chucklever@gmail.com \
--cc=hch@lst.de \
--cc=kbuild-all@01.org \
--cc=linux-nfs@vger.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;
as well as URLs for NNTP newsgroup(s).