From: kernel test robot <lkp@intel.com>
To: Sandeep Maheswaram <quic_c_sanm@quicinc.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Pavankumar Kondeti <quic_pkondeti@quicinc.com>,
Krishna Kurapati <quic_kriskura@quicinc.com>
Subject: [usb:usb-testing 39/44] drivers/usb/dwc3/dwc3-qcom.c:301:23: warning: no previous prototype for function 'dwc3_qcom_read_usb2_speed'
Date: Sat, 11 Jun 2022 19:44:07 +0800 [thread overview]
Message-ID: <202206111907.EvH06x2T-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
head: 477122a1eec325621cefd62da8bd8ac20a66fb8e
commit: 4387ea43e3a9dac058adfe5fc68e0e82750201e5 [39/44] usb: dwc3: qcom: Configure wakeup interrupts during suspend
config: mips-randconfig-r024-20220611 (https://download.01.org/0day-ci/archive/20220611/202206111907.EvH06x2T-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project ff4abe755279a3a47cc416ef80dbc900d9a98a19)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mipsel-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?id=4387ea43e3a9dac058adfe5fc68e0e82750201e5
git remote add usb https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
git fetch --no-tags usb usb-testing
git checkout 4387ea43e3a9dac058adfe5fc68e0e82750201e5
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash drivers/usb/dwc3/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/usb/dwc3/dwc3-qcom.c:301:23: warning: no previous prototype for function 'dwc3_qcom_read_usb2_speed' [-Wmissing-prototypes]
enum usb_device_speed dwc3_qcom_read_usb2_speed(struct dwc3_qcom *qcom)
^
drivers/usb/dwc3/dwc3-qcom.c:301:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
enum usb_device_speed dwc3_qcom_read_usb2_speed(struct dwc3_qcom *qcom)
^
static
1 warning generated.
vim +/dwc3_qcom_read_usb2_speed +301 drivers/usb/dwc3/dwc3-qcom.c
300
> 301 enum usb_device_speed dwc3_qcom_read_usb2_speed(struct dwc3_qcom *qcom)
302 {
303 struct dwc3 *dwc = platform_get_drvdata(qcom->dwc3);
304 struct usb_hcd *hcd = platform_get_drvdata(dwc->xhci);
305 struct usb_device *udev;
306
307 /*
308 * It is possible to query the speed of all children of
309 * USB2.0 root hub via usb_hub_for_each_child(). DWC3 code
310 * currently supports only 1 port per controller. So
311 * this is sufficient.
312 */
313 udev = usb_hub_find_child(hcd->self.root_hub, 1);
314
315 if (!udev)
316 return USB_SPEED_UNKNOWN;
317
318 return udev->speed;
319 }
320
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-11 11:44 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=202206111907.EvH06x2T-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-usb@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=quic_c_sanm@quicinc.com \
--cc=quic_kriskura@quicinc.com \
--cc=quic_pkondeti@quicinc.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