From: kbuild test robot <lkp@intel.com>
To: liaoweixiong <liaoweixiong@allwinnertech.com>
Cc: kbuild-all@01.org, Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org,
liaoweixiong <liaoweixiong@allwinnertech.com>
Subject: Re: [PATCH] pstore: fix crypto dependencies of 842/zstd compression
Date: Mon, 17 Dec 2018 16:16:36 +0800 [thread overview]
Message-ID: <201812171624.Ych15Vum%fengguang.wu@intel.com> (raw)
In-Reply-To: <1544603038-9373-1-git-send-email-liaoweixiong@allwinnertech.com>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
Hi liaoweixiong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on kees/for-next/pstore]
[also build test ERROR on v4.20-rc7 next-20181214]
[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/liaoweixiong/pstore-fix-crypto-dependencies-of-842-zstd-compression/20181214-222645
base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/pstore
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs/pstore/platform.o: In function `zbufsize_zstd':
>> platform.c:(.text+0x30a): undefined reference to `ZSTD_compressBound'
---
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: 66028 bytes --]
next prev parent reply other threads:[~2018-12-17 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 8:23 liaoweixiong
2018-12-12 18:43 ` Kees Cook
2018-12-13 4:39 ` 廖威雄
2018-12-14 1:47 ` 廖威雄
2018-12-17 8:16 ` kbuild test robot [this message]
2018-12-18 8:04 ` 廖威雄
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=201812171624.Ych15Vum%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=liaoweixiong@allwinnertech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®