archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <>
To: kbuild test robot <>
Cc: Andi Kleen <>,,,
Subject: Re: [PATCH v3] x86: Add trace points to (nearly) all vectors
Date: Mon, 4 Nov 2019 17:46:06 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Nov 02, 2019 at 08:47:59AM +0800, kbuild test robot wrote:
> Hi Andi,
> Thank you for the patch! Yet something to improve:
> [auto build test ERROR on tip/auto-latest]
> [also build test ERROR on v5.4-rc5 next-20191031]
> [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]
> url:
> base: a5b576bfb3ba85d3e356f9900dce1428d4760582
> config: i386-tinyconfig (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386 
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <>
> All errors (new ones prefixed by >>):
>    arch/x86/kernel/traps.c: In function 'do_error_trap':
> >> arch/x86/kernel/traps.c:264:2: error: implicit declaration of function 'trace_other_vector_entry'; did you mean 'frame_vector_destroy'? [-Werror=implicit-function-declaration]
>      trace_other_vector_entry(trapnr);
>      ^~~~~~~~~~~~~~~~~~~~~~~~

Also cannot reproduce and the config file seems to be not matching the kernel.

The file has the correct include:

vi +60 arch/x86/kernel/traps.c

 60 #include <asm/trace/irq_vectors.h>


  reply	other threads:[~2019-11-05  1:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 19:56 [PATCH v3] x86: Add trace points to (nearly) all vectors Andi Kleen
2019-11-02  0:47 ` kbuild test robot
2019-11-05  1:46   ` Andi Kleen [this message]
2019-11-07  1:51     ` [kbuild-all] " Rong Chen
2019-11-02  1:24 ` kbuild test robot
2019-11-05  1:44   ` Andi Kleen
2019-11-05 16:55     ` Andi Kleen

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 \ \ \ \ \ \ \ \

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