From: kernel test robot <lkp@intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [djiang:cxl-hmem-report 20/24] drivers/cxl/mem.c:288:3: error: use of undeclared identifier 'dev_attr_mem_qos_class'; did you mean 'dev_attr_pmem_qos_class'?
Date: Mon, 18 Dec 2023 10:15:11 +0800 [thread overview]
Message-ID: <202312181027.SHwTaBA8-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djiang/linux.git cxl-hmem-report
head: da30cd12e1d2c65f67dcdae7cb4842d73184d98e
commit: d1877054cac84876a5263ea668dc0b76d321049d [20/24] fixup missing chunk
config: i386-randconfig-014-20231218 (https://download.01.org/0day-ci/archive/20231218/202312181027.SHwTaBA8-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231218/202312181027.SHwTaBA8-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/202312181027.SHwTaBA8-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/cxl/mem.c:288:3: error: use of undeclared identifier 'dev_attr_mem_qos_class'; did you mean 'dev_attr_pmem_qos_class'?
&dev_attr_mem_qos_class.attr,
^~~~~~~~~~~~~~~~~~~~~~
dev_attr_pmem_qos_class
drivers/cxl/mem.c:261:32: note: 'dev_attr_pmem_qos_class' declared here
static struct device_attribute dev_attr_pmem_qos_class =
^
1 error generated.
vim +288 drivers/cxl/mem.c
285
286 static struct attribute *cxl_mem_attrs[] = {
287 &dev_attr_trigger_poison_list.attr,
> 288 &dev_attr_mem_qos_class.attr,
289 &dev_attr_pmem_qos_class.attr,
290 NULL
291 };
292
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-18 2:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202312181027.SHwTaBA8-lkp@intel.com \
--to=lkp@intel.com \
--cc=dave.jiang@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