From: kbuild test robot <lkp@intel.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: kbuild-all@01.org, live-patching@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/livepatch: introduce tests
Date: Fri, 30 Mar 2018 04:42:56 +0800 [thread overview]
Message-ID: <201803300354.Xrymkh10%fengguang.wu@intel.com> (raw)
In-Reply-To: <1522266588-11806-2-git-send-email-joe.lawrence@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]
Hi Joe,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc7 next-20180329]
[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/Joe-Lawrence/selftests-livepatch-introduce-tests/20180330-004235
config: s390-allyesconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 7.2.0-11) 7.2.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
make.cross ARCH=s390
All errors (new ones prefixed by >>):
lib/livepatch/test_klp_atomic_replace.c: In function 'livepatch_init':
>> lib/livepatch/test_klp_atomic_replace.c:46:7: error: 'struct klp_patch' has no member named 'replace'
patch.replace = replace;
^
--
lib/livepatch/test_klp_callbacks_demo2.c: In function 'livepatch_callbacks_demo2_init':
>> lib/livepatch/test_klp_callbacks_demo2.c:81:7: error: 'struct klp_patch' has no member named 'replace'
patch.replace = replace;
^
vim +46 lib/livepatch/test_klp_atomic_replace.c
41
42 static int livepatch_init(void)
43 {
44 int ret;
45
> 46 patch.replace = replace;
47
48 ret = klp_register_patch(&patch);
49 if (ret)
50 return ret;
51 ret = klp_enable_patch(&patch);
52 if (ret) {
53 WARN_ON(klp_unregister_patch(&patch));
54 return ret;
55 }
56 return 0;
57 }
58
---
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: 49016 bytes --]
next prev parent reply other threads:[~2018-03-29 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 19:49 [PATCH] Add livepatch kselftests Joe Lawrence
2018-03-28 19:49 ` [PATCH] selftests/livepatch: introduce tests Joe Lawrence
2018-03-29 20:42 ` kbuild test robot [this message]
2018-04-07 2:36 ` Josh Poimboeuf
2018-04-08 15:42 ` Joe Lawrence
2018-04-09 14:05 ` Petr Mladek
2018-04-10 14:31 ` Miroslav Benes
2018-04-10 17:51 ` Josh Poimboeuf
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=201803300354.Xrymkh10%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=joe.lawrence@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@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).