From: Andi Kleen <ak@linux.intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3] x86: Add trace points to (nearly) all vectors
Date: Tue, 05 Nov 2019 08:55:17 -0800 [thread overview]
Message-ID: <20191105165517.GA373029@tassilo.jf.intel.com> (raw)
In-Reply-To: <20191105014439.GB25308@tassilo.jf.intel.com>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Mon, Nov 04, 2019 at 05:44:39PM -0800, Andi Kleen wrote:
> 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
Never mind -- the config works with make ARCH=i386
Helps when you read the message completely :-)
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@linux.intel.com>
To: kbuild test robot <lkp@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
kbuild-all@lists.01.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] x86: Add trace points to (nearly) all vectors
Date: Tue, 5 Nov 2019 08:55:17 -0800 [thread overview]
Message-ID: <20191105165517.GA373029@tassilo.jf.intel.com> (raw)
In-Reply-To: <20191105014439.GB25308@tassilo.jf.intel.com>
On Mon, Nov 04, 2019 at 05:44:39PM -0800, Andi Kleen wrote:
> 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
Never mind -- the config works with make ARCH=i386
Helps when you read the message completely :-)
-Andi
next prev parent reply other threads:[~2019-11-05 16:55 UTC|newest]
Thread overview: 13+ 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-02 0:47 ` kbuild test robot
2019-11-05 1:46 ` Andi Kleen
2019-11-05 1:46 ` Andi Kleen
2019-11-07 1:51 ` Rong Chen
2019-11-07 1:51 ` [kbuild-all] " Rong Chen
2019-11-02 1:24 ` kbuild test robot
2019-11-02 1:24 ` kbuild test robot
2019-11-05 1:44 ` Andi Kleen
2019-11-05 1:44 ` Andi Kleen
2019-11-05 16:55 ` 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:
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=20191105165517.GA373029@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.