From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: x86-ml <x86@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [tip:perf/core] BUILD SUCCESS dc39beffcfc19a8dd2a09c5818dcd1a4e9099033
Date: Fri, 28 Oct 2022 00:01:59 +0200 [thread overview]
Message-ID: <Y1r/15SeteYfbFbA@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <635aef44.eRNqJ814AXKXgqPJ%lkp@intel.com>
On Fri, Oct 28, 2022 at 04:51:16AM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
> branch HEAD: dc39beffcfc19a8dd2a09c5818dcd1a4e9099033 perf: Optimize perf_tp_event()
The robot is still broken:
202210272227.jWuKg5y6-lkp@intel.com
next prev parent reply other threads:[~2022-10-27 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 20:51 kernel test robot
2022-10-27 22:01 ` Peter Zijlstra [this message]
2022-10-28 1:21 ` Chen, Rong A
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=Y1r/15SeteYfbFbA@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=x86@kernel.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 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®