Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH V8 2/6] perf: attach/detach PMU specific data
Date: Thu, 13 Mar 2025 16:09:02 +0100	[thread overview]
Message-ID: <20250313150902.GA2418865@ax162> (raw)
In-Reply-To: <202503130756.2j1ZuGT4-lkp@intel.com>

Hi Intel folks,

On Thu, Mar 13, 2025 at 07:46:26AM +0800, kernel test robot wrote:
...
> url:    https://github.com/intel-lab-lkp/linux/commits/kan-liang-linux-intel-com/perf-attach-detach-PMU-specific-data/20250313-022851
> base:   tip/perf/core
> patch link:    https://lore.kernel.org/r/20250312182525.4078433-2-kan.liang%40linux.intel.com
> patch subject: [PATCH V8 2/6] perf: attach/detach PMU specific data
> config: csky-randconfig-002-20250313 (https://download.01.org/0day-ci/archive/20250313/202503130756.2j1ZuGT4-lkp@intel.com/config)
> compiler: csky-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250313/202503130756.2j1ZuGT4-lkp@intel.com/reproduce)

I am noticing a number of recent reports that are being sent to our
mailing list (llvm@lists.linux.dev) when the compiler is not clang, is
something wrong with your filtering? Here are a number of examples:

https://lore.kernel.org/202503130708.AmtUDVfq-lkp@intel.com/
https://lore.kernel.org/202503131646.3EOj6ycs-lkp@intel.com/
https://lore.kernel.org/202503131715.Fb6CfjhT-lkp@intel.com/
https://lore.kernel.org/202503132205.Ajz52k8I-lkp@intel.com/
https://lore.kernel.org/202503132205.Vf8imlWS-lkp@intel.com/
https://lore.kernel.org/202503132256.f6p359iT-lkp@intel.com/

Cheers,
Nathan

  reply	other threads:[~2025-03-13 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250312182525.4078433-2-kan.liang@linux.intel.com>
2025-03-12 23:23 ` [PATCH V8 2/6] perf: attach/detach PMU specific data kernel test robot
2025-03-12 23:46 ` kernel test robot
2025-03-13 15:09   ` Nathan Chancellor [this message]
2025-03-13 23:06     ` Philip Li

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=20250313150902.GA2418865@ax162 \
    --to=nathan@kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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