Linux CXL
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dave Jiang <dave.jiang@intel.com>, linux-cxl@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, dave@stgolabs.net,
	jonathan.cameron@huawei.com, alison.schofield@intel.com,
	vishal.l.verma@intel.com, ira.weiny@intel.com,
	dan.j.williams@intel.com
Subject: Re: [PATCH v2] cxl: Add committed sysfs attribute to CXL decoder
Date: Wed, 27 Sep 2023 02:16:40 +0800	[thread overview]
Message-ID: <202309270116.IH2UP8s4-lkp@intel.com> (raw)
In-Reply-To: <169574219129.3884437.11954592650115343944.stgit@djiang5-mobl3>

Hi Dave,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on cxl/next cxl/pending v6.6-rc3 next-20230926]
[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/Dave-Jiang/cxl-Add-committed-sysfs-attribute-to-CXL-decoder/20230926-233134
base:   linus/master
patch link:    https://lore.kernel.org/r/169574219129.3884437.11954592650115343944.stgit%40djiang5-mobl3
patch subject: [PATCH v2] cxl: Add committed sysfs attribute to CXL decoder
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20230927/202309270116.IH2UP8s4-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230927/202309270116.IH2UP8s4-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/202309270116.IH2UP8s4-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/cxl/core/port.c: In function 'committed_show':
>> drivers/cxl/core/port.c:286:34: warning: format '%d' expects argument of type 'int', but argument 3 has type 'long unsigned int' [-Wformat=]
     286 |         return sysfs_emit(buf, "%d\n",
         |                                 ~^
         |                                  |
         |                                  int
         |                                 %ld


vim +286 drivers/cxl/core/port.c

   280	
   281	static ssize_t committed_show(struct device *dev,
   282				      struct device_attribute *attr, char *buf)
   283	{
   284		struct cxl_decoder *cxld = to_cxl_decoder(dev);
   285	
 > 286		return sysfs_emit(buf, "%d\n",
   287				  FIELD_GET(CXL_DECODER_F_ENABLE, cxld->flags));
   288	}
   289	

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

      parent reply	other threads:[~2023-09-26 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 15:29 [PATCH v2] cxl: Add committed sysfs attribute to CXL decoder Dave Jiang
2023-09-26 17:01 ` Verma, Vishal L
2023-09-26 18:16 ` kernel test robot [this message]

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=202309270116.IH2UP8s4-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox