From: kbuild test robot <lkp@intel.com>
To: Geliang Tang <geliangtang@gmail.com>
Cc: kbuild-all@01.org, Phillip Lougher <phillip@squashfs.org.uk>,
Jonathan Corbet <corbet@lwn.net>,
Geliang Tang <geliangtang@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] squashfs: Add posix acl support
Date: Tue, 10 Apr 2018 04:35:12 +0800 [thread overview]
Message-ID: <201804100217.d2VDp6Fv%fengguang.wu@intel.com> (raw)
In-Reply-To: <af77c1f80e2725c4cf1bf106d6add820b3b0eed5.1523276963.git.geliangtang@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi Geliang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.16]
[also build test ERROR on next-20180409]
[cannot apply to squashfs/master]
[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/Geliang-Tang/squashfs-Add-posix-acl-support/20180410-013038
config: i386-randconfig-s0-201814 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> ERROR: "squashfs_get_acl" [fs/squashfs/squashfs.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: 35602 bytes --]
next prev parent reply other threads:[~2018-04-09 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 12:34 [PATCH] squashfs: Add posix acl support Geliang Tang
2018-04-09 12:34 ` [PATCH] squashfs-tools: " Geliang Tang
2018-04-09 19:39 ` [PATCH] squashfs: " kbuild test robot
2018-04-09 20:35 ` kbuild test robot [this message]
2018-04-10 2:24 ` [PATCH v2] " Geliang Tang
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=201804100217.d2VDp6Fv%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=corbet@lwn.net \
--cc=geliangtang@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@squashfs.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