From: kbuild test robot <lkp@intel.com>
To: Constantine Shulyupin <const@MakeLinux.com>
Cc: kbuild-all@01.org, miklos@szeredi.hu, viro@zeniv.linux.org.uk,
corbet@lwn.net, liushuoran@jd.com,
mitsuo.hayasaka.hu@hitachi.com,
"open list:FUSE: FILESYSTEM IN USERSPACE"
<linux-fsdevel@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
amir73il@gmail.com, Constantine Shulyupin <const@MakeLinux.com>
Subject: Re: [PATCH v3 1/3] fuse: add max_pages option
Date: Wed, 15 Aug 2018 17:21:56 +0800 [thread overview]
Message-ID: <201808151716.NdyijSAs%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180814211717.22170-1-const@MakeLinux.com>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
Hi Constantine,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on fuse/for-next]
[also build test ERROR on v4.18 next-20180814]
[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/Constantine-Shulyupin/fuse-add-max_pages-option/20180815-132537
base: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the linux-review/Constantine-Shulyupin/fuse-add-max_pages-option/20180815-132537 HEAD a01ed7faa3c2a69ef01952ff908d28718edb056c builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
>> ERROR: "pipe_max_size" [fs/fuse/fuse.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: 40815 bytes --]
prev parent reply other threads:[~2018-08-15 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 21:17 [PATCH v3 1/3] fuse: add max_pages option Constantine Shulyupin
2018-08-14 21:17 ` [PATCH v3 2/3] " Constantine Shulyupin
2018-08-14 21:17 ` [PATCH v3 3/3] fuse: export pipe_max_size for max_pages Constantine Shulyupin
2018-08-15 7:56 ` [PATCH v3 1/3] fuse: add max_pages option Miklos Szeredi
2018-08-15 9:21 ` 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=201808151716.NdyijSAs%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=const@MakeLinux.com \
--cc=corbet@lwn.net \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushuoran@jd.com \
--cc=miklos@szeredi.hu \
--cc=mitsuo.hayasaka.hu@hitachi.com \
--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).