From: kbuild test robot <lkp@intel•com>
To: Nathan Chancellor <natechancellor@gmail•com>
Cc: linux-kernel@vger•kernel.org, clang-built-linux@googlegroups•com,
Paul Mackerras <paulus@samba•org>,
kbuild-all@01•org, linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH] powerpc: Test broken dcbz
Date: Mon, 22 Jul 2019 08:53:33 +0800 [thread overview]
Message-ID: <201907220849.f3zL8NEf%lkp@intel.com> (raw)
In-Reply-To: <20190721075846.GA97701@archlinux-threadripper>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
Hi Nathan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc1 next-20190719]
[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/Nathan-Chancellor/powerpc-Test-broken-dcbz/20190722-051054
config: powerpc-defconfig (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=powerpc
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel•com>
All errors (new ones prefixed by >>):
arch/powerpc/mm/mem.c: In function 'clear_user_page':
>> arch/powerpc/mm/mem.c:364:2: error: implicit declaration of function 'broken_clear_page'; did you mean 'bdev_read_page'? [-Werror=implicit-function-declaration]
broken_clear_page(page);
^~~~~~~~~~~~~~~~~
bdev_read_page
cc1: all warnings being treated as errors
vim +364 arch/powerpc/mm/mem.c
---
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: 25327 bytes --]
next prev parent reply other threads:[~2019-07-22 0:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 9:24 [PATCH v2] powerpc: slightly improve cache helpers Christophe Leroy
2019-07-08 1:19 ` Michael Ellerman
2019-07-08 19:14 ` Nathan Chancellor
2019-07-09 5:04 ` Christophe Leroy
2019-07-09 6:49 ` Nathan Chancellor
2019-07-19 3:24 ` Nathan Chancellor
2019-07-19 15:23 ` Segher Boessenkool
2019-07-19 16:04 ` Nathan Chancellor
2019-07-21 7:58 ` Nathan Chancellor
2019-07-21 18:01 ` Segher Boessenkool
2019-07-22 2:41 ` Nathan Chancellor
2019-07-22 6:19 ` Segher Boessenkool
2019-07-22 17:21 ` Nick Desaulniers
2019-07-22 17:58 ` Segher Boessenkool
2019-07-25 21:30 ` Nick Desaulniers
2019-07-29 20:28 ` Nick Desaulniers
2019-07-22 10:15 ` Michael Ellerman
2019-07-22 15:18 ` Segher Boessenkool
2019-07-22 23:21 ` Michael Ellerman
2019-07-25 13:22 ` Segher Boessenkool
2019-07-22 0:53 ` kbuild test robot [this message]
2019-07-09 13:35 ` Segher Boessenkool
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=201907220849.f3zL8NEf%lkp@intel.com \
--to=lkp@intel$(echo .)com \
--cc=clang-built-linux@googlegroups$(echo .)com \
--cc=kbuild-all@01$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=natechancellor@gmail$(echo .)com \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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