From: kbuild test robot <lkp@intel.com>
To: Jinbum Park <jinb.park7@gmail.com>
Cc: kbuild-all@01.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, keescook@chromium.org,
arjan@linux.intel.com, akpm@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
labbott@redhat.com, kernel-hardening@lists.openwall.com,
mark.rutland@arm.com, kernel-janitors@vger.kernel.org,
linux@armlinux.org.uk
Subject: Re: [PATCH v2] mm: add arch-independent testcases for RODATA
Date: Fri, 20 Jan 2017 15:45:44 +0800 [thread overview]
Message-ID: <201701201508.TNgOEXkL%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170119153920.GA20363@pjb1027-Latitude-E5410>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
Hi Jinbum,
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.10-rc4 next-20170119]
[cannot apply to tip/x86/core]
[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/Jinbum-Park/mm-add-arch-independent-testcases-for-RODATA/20170120-134329
base: git://git.cmpxchg.org/linux-mmotm.git master
config: x86_64-nfsroot (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> ERROR: "rodata_test_data" [arch/x86/kernel/test_nx.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: 26744 bytes --]
prev parent reply other threads:[~2017-01-20 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 15:39 Jinbum Park
2017-01-19 15:46 ` Russell King - ARM Linux
2017-01-20 7:45 ` 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=201701201508.TNgOEXkL%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linuxfoundation.org \
--cc=arjan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jinb.park7@gmail.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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