From: kernel test robot <lkp@intel.com>
To: Badhri Jagan Sridharan <badhri@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: [stable:linux-6.1.y 6854/8698] drivers/usb/gadget/udc/core.c:56: warning: Function parameter or member 'vbus_work' not described in 'usb_udc'
Date: Fri, 18 Aug 2023 12:41:40 +0800 [thread overview]
Message-ID: <202308181228.oUyNPyxW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.1.y
head: 6c44e13dc284f7f4db17706ca48fd016d6b3d49a
commit: 3c048d42c305cba61c2040702778023a7b973b22 [6854/8698] usb: gadget: udc: core: Offload usb_udc_vbus_handler processing
config: i386-randconfig-i001-20230817 (https://download.01.org/0day-ci/archive/20230818/202308181228.oUyNPyxW-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce: (https://download.01.org/0day-ci/archive/20230818/202308181228.oUyNPyxW-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/202308181228.oUyNPyxW-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/usb/gadget/udc/core.c:56: warning: Function parameter or member 'vbus_work' not described in 'usb_udc'
vim +56 drivers/usb/gadget/udc/core.c
fc274c1e997314 drivers/usb/gadget/udc/core.c Alan Stern 2022-04-23 30
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 31 /**
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 32 * struct usb_udc - describes one usb device controller
e21cd08f965766 drivers/usb/gadget/udc/core.c Lee Jones 2020-07-03 33 * @driver: the gadget driver pointer. For use by the class code
e21cd08f965766 drivers/usb/gadget/udc/core.c Lee Jones 2020-07-03 34 * @dev: the child device to the actual controller
e21cd08f965766 drivers/usb/gadget/udc/core.c Lee Jones 2020-07-03 35 * @gadget: the gadget. For use by the class code
e21cd08f965766 drivers/usb/gadget/udc/core.c Lee Jones 2020-07-03 36 * @list: for use by the udc class driver
e21cd08f965766 drivers/usb/gadget/udc/core.c Lee Jones 2020-07-03 37 * @vbus: for udcs who care about vbus status, this value is real vbus status;
628ef0d273a69d drivers/usb/gadget/udc/udc-core.c Peter Chen 2015-03-06 38 * for udcs who do not care about vbus status, this value is always true
49d08cfc783044 drivers/usb/gadget/udc/core.c Thinh Nguyen 2021-01-11 39 * @started: the UDC's started state. True if the UDC had started.
3c048d42c305cb drivers/usb/gadget/udc/core.c Badhri Jagan Sridharan 2023-06-09 40 * @allow_connect: Indicates whether UDC is allowed to be pulled up.
3c048d42c305cb drivers/usb/gadget/udc/core.c Badhri Jagan Sridharan 2023-06-09 41 * Set/cleared by gadget_(un)bind_driver() after gadget driver is bound or
3c048d42c305cb drivers/usb/gadget/udc/core.c Badhri Jagan Sridharan 2023-06-09 42 * unbound.
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 43 *
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 44 * This represents the internal data structure which is used by the UDC-class
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 45 * to hold information about udc driver and gadget together.
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 46 */
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 47 struct usb_udc {
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 48 struct usb_gadget_driver *driver;
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 49 struct usb_gadget *gadget;
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 50 struct device dev;
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 51 struct list_head list;
628ef0d273a69d drivers/usb/gadget/udc/udc-core.c Peter Chen 2015-03-06 52 bool vbus;
49d08cfc783044 drivers/usb/gadget/udc/core.c Thinh Nguyen 2021-01-11 53 bool started;
3c048d42c305cb drivers/usb/gadget/udc/core.c Badhri Jagan Sridharan 2023-06-09 54 bool allow_connect;
3c048d42c305cb drivers/usb/gadget/udc/core.c Badhri Jagan Sridharan 2023-06-09 55 struct work_struct vbus_work;
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 @56 };
2ccea03a8f7ec9 drivers/usb/gadget/udc-core.c Felipe Balbi 2011-06-28 57
:::::: The code at line 56 was first introduced by commit
:::::: 2ccea03a8f7ec93641791f2760d7cdc6cab6205f usb: gadget: introduce UDC Class
:::::: TO: Felipe Balbi <balbi@ti.com>
:::::: CC: Greg Kroah-Hartman <gregkh@suse.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-18 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 4:41 kernel test robot [this message]
2023-08-18 13:52 ` [stable:linux-6.1.y 6854/8698] drivers/usb/gadget/udc/core.c:56: warning: Function parameter or member 'vbus_work' not described in 'usb_udc' Alan Stern
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=202308181228.oUyNPyxW-lkp@intel.com \
--to=lkp@intel.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).