linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Bjorn Helgaas <helgaas@kernel.org>
Subject: [linux-next:pending-fixes 269/310] drivers/pci/bus.c:440: warning: Function parameter or struct member 'top' not described in 'pci_walk_bus'
Date: Wed, 31 Jan 2024 09:36:38 +0800	[thread overview]
Message-ID: <202401310949.NbpFjuGe-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
head:   60b9561aaa2811b5bff20d52b08d72bd2183f7cb
commit: 69fb843fdbd91d283773e054df20c420d7bddcd8 [269/310] PCI/ASPM: Fix deadlock when enabling ASPM
config: parisc-defconfig (https://download.01.org/0day-ci/archive/20240131/202401310949.NbpFjuGe-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240131/202401310949.NbpFjuGe-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/202401310949.NbpFjuGe-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/pci/bus.c:440: warning: Function parameter or struct member 'top' not described in 'pci_walk_bus'
>> drivers/pci/bus.c:440: warning: Function parameter or struct member 'cb' not described in 'pci_walk_bus'
>> drivers/pci/bus.c:440: warning: Function parameter or struct member 'userdata' not described in 'pci_walk_bus'


vim +440 drivers/pci/bus.c

   425	
   426	/**
   427	 *  pci_walk_bus - walk devices on/under bus, calling callback.
   428	 *  @top      bus whose devices should be walked
   429	 *  @cb       callback to be called for each device found
   430	 *  @userdata arbitrary pointer to be passed to callback.
   431	 *
   432	 *  Walk the given bus, including any bridged devices
   433	 *  on buses under this bus.  Call the provided callback
   434	 *  on each device found.
   435	 *
   436	 *  We check the return of @cb each time. If it returns anything
   437	 *  other than 0, we break out.
   438	 */
   439	void pci_walk_bus(struct pci_bus *top, int (*cb)(struct pci_dev *, void *), void *userdata)
 > 440	{
   441		__pci_walk_bus(top, cb, userdata, false);
   442	}
   443	EXPORT_SYMBOL_GPL(pci_walk_bus);
   444	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2024-01-31  1:36 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=202401310949.NbpFjuGe-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=helgaas@kernel.org \
    --cc=johan+linaro@kernel.org \
    --cc=linux-mm@kvack.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