From: kernel test robot <lkp@intel.com>
To: Ryan Chung <seokwoo.chung130@gmail.com>,
hao.wu@intel.com, trix@redhat.com, mdf@kernel.org,
yilun.xu@intel.com
Cc: oe-kbuild-all@lists.linux.dev, linux-fpga@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
linux-kernel@vger.kernel.org,
Ryan Chung <seokwoo.chung130@gmail.com>
Subject: Re: [PATCH] fpga: dfl: Replace scnprintf() with sysfs_emit()
Date: Tue, 1 Jul 2025 19:02:28 +0800 [thread overview]
Message-ID: <202507011805.BSIqVlhe-lkp@intel.com> (raw)
In-Reply-To: <20250630125018.48417-1-seokwoo.chung130@gmail.com>
Hi Ryan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.16-rc4 next-20250630]
[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/Ryan-Chung/fpga-dfl-Replace-scnprintf-with-sysfs_emit/20250630-205221
base: linus/master
patch link: https://lore.kernel.org/r/20250630125018.48417-1-seokwoo.chung130%40gmail.com
patch subject: [PATCH] fpga: dfl: Replace scnprintf() with sysfs_emit()
config: sparc-randconfig-r112-20250701 (https://download.01.org/0day-ci/archive/20250701/202507011805.BSIqVlhe-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 8.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250701/202507011805.BSIqVlhe-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/202507011805.BSIqVlhe-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/fpga/dfl-afu-main.c:159:32: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected char const *fmt @@ got unsigned long @@
drivers/fpga/dfl-afu-main.c:159:32: sparse: expected char const *fmt
drivers/fpga/dfl-afu-main.c:159:32: sparse: got unsigned long
drivers/fpga/dfl-afu-main.c:478:32: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected char const *fmt @@ got unsigned long @@
drivers/fpga/dfl-afu-main.c:478:32: sparse: expected char const *fmt
drivers/fpga/dfl-afu-main.c:478:32: sparse: got unsigned long
vim +159 drivers/fpga/dfl-afu-main.c
152
153 static ssize_t
154 id_show(struct device *dev, struct device_attribute *attr, char *buf)
155 {
156 struct dfl_feature_dev_data *fdata = to_dfl_feature_dev_data(dev);
157 int id = port_get_id(fdata);
158
> 159 return sysfs_emit(buf, PAGE_SIZE, "%d\n", id);
160 }
161 static DEVICE_ATTR_RO(id);
162
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-07-01 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 12:50 [PATCH] fpga: dfl: Replace scnprintf() with sysfs_emit() Ryan Chung
2025-06-30 13:15 ` Greg KH
2025-07-01 4:09 ` kernel test robot
2025-07-01 4:30 ` kernel test robot
2025-07-01 11:02 ` 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=202507011805.BSIqVlhe-lkp@intel.com \
--to=lkp@intel.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seokwoo.chung130@gmail.com \
--cc=trix@redhat.com \
--cc=yilun.xu@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