From: kernel test robot <lkp@intel.com>
To: Pawel Laszczak <pawell@cadence.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: oe-kbuild-all@lists.linux.dev,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
"christophe.jaillet@wanadoo.fr" <christophe.jaillet@wanadoo.fr>,
"javier.carrasco@wolfvision.net" <javier.carrasco@wolfvision.net>,
"make_ruc2021@163.com" <make_ruc2021@163.com>,
"peter.chen@nxp.com" <peter.chen@nxp.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pawel Eichler <peichler@cadence.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] usb: xhci: lack of clearing xHC resources
Date: Thu, 27 Feb 2025 16:10:52 +0800 [thread overview]
Message-ID: <202502271523.jt3l4VVu-lkp@intel.com> (raw)
In-Reply-To: <PH7PR07MB95385E2766D01F3741D418ABDDC22@PH7PR07MB9538.namprd07.prod.outlook.com>
Hi Pawel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on usb/usb-next usb/usb-linus linus/master v6.14-rc4]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Pawel-Laszczak/usb-xhci-lack-of-clearing-xHC-resources/20250226-153837
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
patch link: https://lore.kernel.org/r/PH7PR07MB95385E2766D01F3741D418ABDDC22%40PH7PR07MB9538.namprd07.prod.outlook.com
patch subject: [PATCH v2] usb: xhci: lack of clearing xHC resources
config: i386-buildonly-randconfig-001-20250227 (https://download.01.org/0day-ci/archive/20250227/202502271523.jt3l4VVu-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250227/202502271523.jt3l4VVu-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/202502271523.jt3l4VVu-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/usb/core/hub.c:6084: warning: Function parameter or struct member 'udev' not described in 'hub_hc_release_resources'
>> drivers/usb/core/hub.c:6084: warning: Excess function parameter 'pdev' description in 'hub_hc_release_resources'
vim +6084 drivers/usb/core/hub.c
6067
6068 /**
6069 * hub_hc_release_resources - clear resources used by host controller
6070 * @pdev: pointer to device being released
6071 *
6072 * Context: task context, might sleep
6073 *
6074 * Function releases the host controller resources in correct order before
6075 * making any operation on resuming usb device. The host controller resources
6076 * allocated for devices in tree should be released starting from the last
6077 * usb device in tree toward the root hub. This function is used only during
6078 * resuming device when usb device require reinitialization - that is, when
6079 * flag udev->reset_resume is set.
6080 *
6081 * This call is synchronous, and may not be used in an interrupt context.
6082 */
6083 static void hub_hc_release_resources(struct usb_device *udev)
> 6084 {
6085 struct usb_hub *hub = usb_hub_to_struct_hub(udev);
6086 struct usb_hcd *hcd = bus_to_hcd(udev->bus);
6087 int i;
6088
6089 /* Release up resources for all children before this device */
6090 for (i = 0; i < udev->maxchild; i++)
6091 if (hub->ports[i]->child)
6092 hub_hc_release_resources(hub->ports[i]->child);
6093
6094 if (hcd->driver->reset_device)
6095 hcd->driver->reset_device(hcd, udev);
6096 }
6097
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-02-27 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250226071646.4034220-1-pawell@cadence.com>
2025-02-26 7:23 ` Pawel Laszczak
2025-02-26 15:47 ` stern
2025-02-27 7:05 ` Pawel Laszczak
2025-02-27 15:12 ` stern
2025-02-27 8:10 ` kernel test robot [this message]
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=202502271523.jt3l4VVu-lkp@intel.com \
--to=lkp@intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gregkh@linuxfoundation.org \
--cc=javier.carrasco@wolfvision.net \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=make_ruc2021@163.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pawell@cadence.com \
--cc=peichler@cadence.com \
--cc=peter.chen@nxp.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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®