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:44:39 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Nov 02, 2019 at 09:24:50AM +0800, kbuild test robot wrote:
> Hi Andi,
> Thank you for the patch! Yet something to improve:

I cannot reproduce this.

And the file clearly has an include for the trace file, so I can't see what
could be wrong.

> [auto build test ERROR on tip/auto-latest]
> [also build test ERROR on v5.4-rc5 next-20191031]

Also the config the bot sent doesn't even match next-20191031 nor tip/auto-latest

$ git log --oneline
5be9e3ebd480 (HEAD) x86: Add trace points to (nearly) all vectors
49afce6d47fe (tag: next-20191031, next/master) Add linux-next specific files for 20191031
$ zcat ~/submit/0day2.config.gz > .config
$ make oldconfig
  GEN     Makefile
scripts/kconfig/conf  --oldconfig Kconfig
* Restart config...
* CPU/Task time and stats accounting
Cputime accounting
> 1. Simple tick based cputime accounting (TICK_CPU_ACCOUNTING)
  2. Full dynticks CPU time accounting (VIRT_CPU_ACCOUNTING_GEN) (NEW)

and lots more of those.

If i press return it compiles fine.

> [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]

My patch was against Linus master, but it should work against all of those


  reply	other threads:[~2019-11-05  1:44 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
2019-11-07  1:51     ` [kbuild-all] " Rong Chen
2019-11-02  1:24 ` kbuild test robot
2019-11-05  1:44   ` Andi Kleen [this message]
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).