LKML Archive on
help / color / mirror / Atom feed
From: kbuild test robot <>
To: Hans de Goede <>
Cc:, Thomas Gleixner <>,
	Ingo Molnar <>, Borislav Petkov <>,
	"H . Peter Anvin" <>,
	Hans de Goede <>,,
Subject: Re: [PATCH resend] x86/purgatory: Make sure we fail the build if has missing symbols
Date: Sun, 1 Mar 2020 01:16:16 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

Hi Hans,

I love your patch! Yet something to improve:

[auto build test ERROR on tip/x86/core]
[also build test ERROR on v5.6-rc3 next-20200228]
[cannot apply to tip/auto-latest]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see]

base: 248ed51048c40d36728e70914e38bffd7821da57
config: x86_64-randconfig-s1-20200229 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.2-10+deb8u1) 4.9.2
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <>

All errors (new ones prefixed by >>):

   ld: arch/x86/purgatory/ in function `kstrtoull':
>> (.text+0x2b0e): undefined reference to `ftrace_likely_update'

0-DAY CI Kernel Test Service, Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40199 bytes --]

  reply	other threads:[~2020-02-29 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 16:59 Hans de Goede
2020-02-29 17:16 ` kbuild test robot [this message]
2020-02-29 18:12   ` Hans de Goede
2020-03-11 20:49     ` Borislav Petkov
2020-03-11 21:20       ` Arvind Sankar
2020-03-11 21:25         ` Hans de Goede
  -- strict thread matches above, loose matches on Subject: below --
2019-12-12 20:50 Hans de Goede

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH resend] x86/purgatory: Make sure we fail the build if has missing symbols' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).