From: kbuild test robot <lkp@intel.com>
To: Matt Rickard <matt@softrans.com.au>
Cc: kbuild-all@01.org, Matt Rickard <matt@softrans.com.au>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH] x86/vdso: Handle clock_gettime(CLOCK_TAI) in vDSO
Date: Fri, 17 Aug 2018 21:08:54 +0800 [thread overview]
Message-ID: <201808172052.1HtKod2c%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180817120944.2A36A18E01A1@virtux64.softrans.com.au>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
Hi Matt,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/x86/vdso]
[also build test ERROR on v4.18 next-20180817]
[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/Matt-Rickard/x86-vdso-Handle-clock_gettime-CLOCK_TAI-in-vDSO/20180817-202932
config: i386-randconfig-x002-201832 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> arch/x86/entry/vdso/vdso32.so.dbg: undefined symbols found
---
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: 31747 bytes --]
next prev parent reply other threads:[~2018-08-17 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 12:09 Matt Rickard
2018-08-17 13:08 ` kbuild test robot [this message]
2018-08-17 13:24 ` kbuild test robot
[not found] <20180817121251.4EB5318E01A1@virtux64.softrans.com.au>
2018-08-24 17:47 ` Andy Lutomirski
2018-08-24 18:25 ` John Stultz
2018-08-28 15:36 ` Matthew Rickard
2018-08-31 18:45 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2018-08-17 12:09 Matt Rickard
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=201808172052.1HtKod2c%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@softrans.com.au \
/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®