All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Shiyang Ruan <ruansy.fnst@fujitsu.com>,
	qemu-devel@nongnu.org, linux-cxl@vger.kernel.org,
	linux-edac@vger.kernel.org, linux-mm@kvack.org,
	dan.j.williams@intel.com, vishal.l.verma@intel.com,
	Jonathan.Cameron@huawei.com, alison.schofield@intel.com
Cc: oe-kbuild-all@lists.linux.dev, bp@alien8.de,
	dave.jiang@intel.com, dave@stgolabs.net, ira.weiny@intel.com,
	james.morse@arm.com, linmiaohe@huawei.com, mchehab@kernel.org,
	nao.horiguchi@gmail.com, rric@kernel.org, tony.luck@intel.com,
	ruansy.fnst@fujitsu.com
Subject: Re: [PATCH v4 2/2] cxl: avoid duplicated report from MCE & device
Date: Fri, 9 Aug 2024 19:48:11 +0800	[thread overview]
Message-ID: <202408091914.TFbjPuNQ-lkp@intel.com> (raw)
In-Reply-To: <20240808151328.707869-3-ruansy.fnst@fujitsu.com>

Hi Shiyang,

kernel test robot noticed the following build warnings:

[auto build test WARNING on tip/x86/core]
[also build test WARNING on cxl/next linus/master v6.11-rc2 next-20240809]
[cannot apply to cxl/pending]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Shiyang-Ruan/cxl-core-introduce-device-reporting-poison-hanlding/20240809-013658
base:   tip/x86/core
patch link:    https://lore.kernel.org/r/20240808151328.707869-3-ruansy.fnst%40fujitsu.com
patch subject: [PATCH v4 2/2] cxl: avoid duplicated report from MCE & device
config: x86_64-randconfig-121-20240809 (https://download.01.org/0day-ci/archive/20240809/202408091914.TFbjPuNQ-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240809/202408091914.TFbjPuNQ-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202408091914.TFbjPuNQ-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/cxl/core/mbox.c:1465:1: sparse: sparse: symbol 'cxl_mce_records' was not declared. Should it be static?
   drivers/cxl/core/mbox.c: note: in included file (through include/linux/gfp.h, include/linux/xarray.h, include/linux/list_lru.h, ...):
   include/linux/mmzone.h:2018:40: sparse: sparse: self-comparison always evaluates to false

vim +/cxl_mce_records +1465 drivers/cxl/core/mbox.c

  1464	
> 1465	DEFINE_XARRAY(cxl_mce_records);
  1466	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2024-08-09 11:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 15:13 [PATCH v4 0/2] cxl: add device reporting poison handler Shiyang Ruan
2024-08-08 15:13 ` Shiyang Ruan via
2024-08-08 15:13 ` [PATCH v4 1/2] cxl/core: introduce device reporting poison hanlding Shiyang Ruan
2024-08-08 15:13   ` Shiyang Ruan via
2024-08-08 18:28   ` Fan Ni
2024-08-21 13:57     ` Shiyang Ruan
2024-08-21 13:57       ` Shiyang Ruan via
2024-08-27 15:46   ` Jonathan Cameron
2024-09-02 14:03     ` Shiyang Ruan
2024-08-08 15:13 ` [PATCH v4 2/2] cxl: avoid duplicated report from MCE & device Shiyang Ruan
2024-08-08 15:13   ` Shiyang Ruan via
2024-08-09  7:31   ` kernel test robot
2024-08-09  7:31   ` kernel test robot
2024-08-09 11:48   ` kernel test robot [this message]
2024-08-27 15:52   ` Jonathan Cameron
2024-09-02 14:19     ` Shiyang Ruan

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=202408091914.TFbjPuNQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=james.morse@arm.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mchehab@kernel.org \
    --cc=nao.horiguchi@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=qemu-devel@nongnu.org \
    --cc=rric@kernel.org \
    --cc=ruansy.fnst@fujitsu.com \
    --cc=tony.luck@intel.com \
    --cc=vishal.l.verma@intel.com \
    /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.