From: kernel test robot <lkp@intel.com>
To: Ayush Singh <ayush@beagleboard.org>,
Jason Kridner <jkridner@beagleboard.org>,
Deepak Khatri <lorforlinux@beagleboard.org>,
Robert Nelson <robertcnelson@beagleboard.org>,
Dhruva Gole <d-gole@ti.com>, Viresh Kumar <vireshk@kernel.org>,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: oe-kbuild-all@lists.linux.dev, greybus-dev@lists.linaro.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Ayush Singh <ayush@beagleboard.org>
Subject: Re: [PATCH] staging: greybus: fw-download: Fix find firmware req
Date: Thu, 23 Oct 2025 12:57:03 +0800 [thread overview]
Message-ID: <202510231209.JEFfW9s0-lkp@intel.com> (raw)
In-Reply-To: <20251022-gb-fw-v1-1-183b18500cd5@beagleboard.org>
Hi Ayush,
kernel test robot noticed the following build warnings:
[auto build test WARNING on aaa9c3550b60d6259d6ea8b1175ade8d1242444e]
url: https://github.com/intel-lab-lkp/linux/commits/Ayush-Singh/staging-greybus-fw-download-Fix-find-firmware-req/20251022-153520
base: aaa9c3550b60d6259d6ea8b1175ade8d1242444e
patch link: https://lore.kernel.org/r/20251022-gb-fw-v1-1-183b18500cd5%40beagleboard.org
patch subject: [PATCH] staging: greybus: fw-download: Fix find firmware req
config: arm64-randconfig-002-20251023 (https://download.01.org/0day-ci/archive/20251023/202510231209.JEFfW9s0-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251023/202510231209.JEFfW9s0-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/202510231209.JEFfW9s0-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/staging/greybus/fw-download.c:14:
drivers/staging/greybus/fw-download.c: In function 'gb_fw_download_request_handler':
>> drivers/staging/greybus/firmware.h:14:24: warning: '%s' directive output may be truncated writing up to 9 bytes into a region of size between 6 and 15 [-Wformat-truncation=]
#define FW_NAME_PREFIX "gmp_"
^~~~~~
drivers/staging/greybus/fw-download.c:188:5: note: in expansion of macro 'FW_NAME_PREFIX'
FW_NAME_PREFIX "%08x_%08x_%08x_%08x_%s.%s",
^~~~~~~~~~~~~~
drivers/staging/greybus/fw-download.c:188:44: note: format string is defined here
FW_NAME_PREFIX "%08x_%08x_%08x_%08x_%s.%s",
^~
drivers/staging/greybus/fw-download.c:187:3: note: 'snprintf' output between 42 and 60 bytes into a destination of size 56
snprintf(fw_req->name, sizeof(fw_req->name),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FW_NAME_PREFIX "%08x_%08x_%08x_%08x_%s.%s",
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
intf->ddbl1_manufacturer_id, intf->ddbl1_product_id,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
intf->vendor_id, intf->product_id, tag, format);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +14 drivers/staging/greybus/firmware.h
cca222076738962 Viresh Kumar 2016-04-28 13
350e3ac2ceb6964 Joel Porquet 2016-07-21 @14 #define FW_NAME_PREFIX "gmp_"
8a704565ebda960 Greg Kroah-Hartman 2016-07-20 15
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-23 4:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 7:27 [PATCH] staging: greybus: fw-download: Fix find firmware req Ayush Singh
2025-10-22 12:03 ` Dan Carpenter
2025-10-22 13:52 ` Ayush Singh
2025-10-22 14:10 ` Dan Carpenter
2025-10-22 14:26 ` Ayush Singh
2025-10-22 14:53 ` Dan Carpenter
2025-10-23 4:57 ` kernel test robot [this message]
2025-10-23 10:04 ` Greg Kroah-Hartman
2025-10-23 11:26 ` Ayush Singh
2025-10-24 16:35 ` Alex Elder
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=202510231209.JEFfW9s0-lkp@intel.com \
--to=lkp@intel.com \
--cc=ayush@beagleboard.org \
--cc=d-gole@ti.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jkridner@beagleboard.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lorforlinux@beagleboard.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robertcnelson@beagleboard.org \
--cc=vireshk@kernel.org \
/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