From: kernel test robot <lkp@intel.com>
To: Tobias Waldekranz <tobias@waldekranz.com>,
davem@davemloft.net, kuba@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
jiri@resnulli.us, ivecera@redhat.com, netdev@vger.kernel.org,
roopa@nvidia.com, razor@blackwall.org, bridge@lists.linux.dev,
rostedt@goodmis.org, mhiramat@kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 3/5] net: switchdev: Relay all replay messages through a central function
Date: Fri, 26 Jan 2024 14:07:27 +0800 [thread overview]
Message-ID: <202401261325.D8Hg7ign-lkp@intel.com> (raw)
In-Reply-To: <20240123153707.550795-4-tobias@waldekranz.com>
Hi Tobias,
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/Tobias-Waldekranz/net-switchdev-Wrap-enums-in-mapper-macros/20240123-234801
base: net-next/main
patch link: https://lore.kernel.org/r/20240123153707.550795-4-tobias%40waldekranz.com
patch subject: [PATCH net-next 3/5] net: switchdev: Relay all replay messages through a central function
config: i386-buildonly-randconfig-003-20240126 (https://download.01.org/0day-ci/archive/20240126/202401261325.D8Hg7ign-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240126/202401261325.D8Hg7ign-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/202401261325.D8Hg7ign-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/switchdev/switchdev.c:322: warning: Function parameter or struct member 'type' not described in 'switchdev_call_replay'
>> net/switchdev/switchdev.c:322: warning: expecting prototype for switchdev_replay(). Prototype was for switchdev_call_replay() instead
vim +322 net/switchdev/switchdev.c
309
310 /**
311 * switchdev_replay - Replay switchdev message to driver
312 * @nb: notifier block to send the message to
313 * @val: value passed unmodified to notifier function
314 * @info: notifier information data
315 *
316 * Typically issued by the bridge, as a response to a replay
317 * request initiated by a port that is either attaching to, or
318 * detaching from, that bridge.
319 */
320 int switchdev_call_replay(struct notifier_block *nb, unsigned long type,
321 struct switchdev_notifier_info *info)
> 322 {
323 return nb->notifier_call(nb, type, info);
324 }
325 EXPORT_SYMBOL_GPL(switchdev_call_replay);
326
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-01-26 6:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 15:37 [PATCH net-next 0/5] net: switchdev: Tracepoints Tobias Waldekranz
2024-01-23 15:37 ` [PATCH net-next 1/5] net: switchdev: Wrap enums in mapper macros Tobias Waldekranz
2024-01-23 15:37 ` [PATCH net-next 2/5] net: switchdev: Add helpers to display switchdev objects as strings Tobias Waldekranz
2024-01-23 15:37 ` [PATCH net-next 3/5] net: switchdev: Relay all replay messages through a central function Tobias Waldekranz
2024-01-24 10:14 ` Simon Horman
2024-01-26 6:07 ` kernel test robot [this message]
2024-01-23 15:37 ` [PATCH net-next 4/5] net: switchdev: Prepare deferred notifications before enqueuing them Tobias Waldekranz
2024-01-23 15:37 ` [PATCH net-next 5/5] net: switchdev: Add tracepoints Tobias Waldekranz
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=202401261325.D8Hg7ign-lkp@intel.com \
--to=lkp@intel.com \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=rostedt@goodmis.org \
--cc=tobias@waldekranz.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).