From: kernel test robot <lkp@intel.com>
To: Ivan Vecera <ivecera@redhat.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Jiri Pirko <jiri@resnulli.us>, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Schmidt <mschmidt@redhat.com>,
Petr Oros <poros@redhat.com>
Subject: Re: [PATCH net-next v5 2/5] dpll: zl3073x: Add low-level flash functions
Date: Tue, 9 Sep 2025 10:03:13 +0800 [thread overview]
Message-ID: <202509090902.7k4O454a-lkp@intel.com> (raw)
In-Reply-To: <20250908093924.1952317-3-ivecera@redhat.com>
Hi Ivan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Ivan-Vecera/dpll-zl3073x-Add-functions-to-access-hardware-registers/20250908-174338
base: net-next/main
patch link: https://lore.kernel.org/r/20250908093924.1952317-3-ivecera%40redhat.com
patch subject: [PATCH net-next v5 2/5] dpll: zl3073x: Add low-level flash functions
config: s390-randconfig-001-20250909 (https://download.01.org/0day-ci/archive/20250909/202509090902.7k4O454a-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250909/202509090902.7k4O454a-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/202509090902.7k4O454a-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/dpll/zl3073x/flash.c:42 function parameter 'component' not described in 'zl3073x_flash_download'
>> Warning: drivers/dpll/zl3073x/flash.c:42 function parameter 'addr' not described in 'zl3073x_flash_download'
>> Warning: drivers/dpll/zl3073x/flash.c:42 function parameter 'data' not described in 'zl3073x_flash_download'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-09 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 9:39 [PATCH net-next v5 0/5] dpll: zl3073x: Add support for devlink flash Ivan Vecera
2025-09-08 9:39 ` [PATCH net-next v5 1/5] dpll: zl3073x: Add functions to access hardware registers Ivan Vecera
2025-09-08 9:39 ` [PATCH net-next v5 2/5] dpll: zl3073x: Add low-level flash functions Ivan Vecera
2025-09-09 2:03 ` kernel test robot [this message]
2025-09-08 9:39 ` [PATCH net-next v5 3/5] dpll: zl3073x: Add firmware loading functionality Ivan Vecera
2025-09-08 9:39 ` [PATCH net-next v5 4/5] dpll: zl3073x: Refactor DPLL initialization Ivan Vecera
2025-09-08 9:39 ` [PATCH net-next v5 5/5] dpll: zl3073x: Implement devlink flash callback Ivan Vecera
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=202509090902.7k4O454a-lkp@intel.com \
--to=lkp@intel.com \
--cc=Prathosh.Satish@microchip.com \
--cc=corbet@lwn.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=przemyslaw.kitszel@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