From: kernel test robot <lkp@intel.com>
To: Helge Deller <deller@gmx.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: arch/parisc/kernel/drivers.c:745:19-20: Unneeded semicolon
Date: Mon, 22 Jan 2024 20:20:25 +0800 [thread overview]
Message-ID: <202401222059.Wli6OGT0-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 6613476e225e090cc9aad49be7fa504e290dd33d
commit: ac9fb7d2b71d8353603534a5e5cc92f54fd7e219 parisc: drivers: Fix kdoc warnings
date: 7 months ago
config: parisc-randconfig-r062-20240122 (https://download.01.org/0day-ci/archive/20240122/202401222059.Wli6OGT0-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
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/202401222059.Wli6OGT0-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> arch/parisc/kernel/drivers.c:745:19-20: Unneeded semicolon
vim +745 arch/parisc/kernel/drivers.c
720
721 /**
722 * parse_tree_node - returns a device entry in the iotree
723 * @parent: the parent node in the tree
724 * @index: the current BC index
725 * @modpath: the hardware_path struct to match a device against
726 * @return: The corresponding device if found, NULL otherwise.
727 *
728 * Checks all the children of @parent for a matching @id. If none
729 * found, it returns NULL.
730 */
731 static struct device *
732 parse_tree_node(struct device *parent, int index, struct hardware_path *modpath)
733 {
734 struct parse_tree_data d = {
735 .index = index,
736 .modpath = modpath,
737 };
738
739 struct recurse_struct recurse_data = {
740 .obj = &d,
741 .fn = check_parent,
742 };
743
744 if (device_for_each_child(parent, &recurse_data, descend_children))
> 745 { /* nothing */ };
746
747 return d.dev;
748 }
749
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-22 12:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202401222059.Wli6OGT0-lkp@intel.com \
--to=lkp@intel.com \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®