All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android-4.19-stable 11093/30000] drivers/usb/gadget/udc/core.c:517: warning: Function parameter or member 'ep' not described in 'usb_gsi_ep_op'
Date: Thu, 12 Dec 2024 20:21:38 +0800	[thread overview]
Message-ID: <202412122006.XUaCvCQa-lkp@intel.com> (raw)

Hi Hridya,

FYI, the error/warning still remains.

tree:   https://android.googlesource.com/kernel/common android-4.19-stable
head:   a8bf86a0e0fa05070897a210d706d5c4d83c26ac
commit: 632093eced49c76aa97f564248efc6d041779135 [11093/30000] ANDROID: GKI: USB: Resolve ABI diff for usb_gadget and usb_gadget_ops
config: arm-randconfig-001-20241212 (https://download.01.org/0day-ci/archive/20241212/202412122006.XUaCvCQa-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241212/202412122006.XUaCvCQa-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/202412122006.XUaCvCQa-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/usb/gadget/udc/core.c:25: warning: Incorrect use of kernel-doc format:  * struct usb_udc - describes one usb device controller
   drivers/usb/gadget/udc/core.c:36: warning: cannot understand function prototype: 'struct usb_udc '
>> drivers/usb/gadget/udc/core.c:517: warning: Function parameter or member 'ep' not described in 'usb_gsi_ep_op'
>> drivers/usb/gadget/udc/core.c:517: warning: Function parameter or member 'req' not described in 'usb_gsi_ep_op'
>> drivers/usb/gadget/udc/core.c:517: warning: Function parameter or member 'op' not described in 'usb_gsi_ep_op'
   drivers/usb/gadget/udc/core.c:933: warning: Function parameter or member 'ep' not described in 'usb_gadget_giveback_request'
   drivers/usb/gadget/udc/core.c:933: warning: Function parameter or member 'req' not described in 'usb_gadget_giveback_request'
   drivers/usb/gadget/udc/core.c:1130: warning: Function parameter or member 'udc' not described in 'usb_gadget_udc_stop'
   drivers/usb/gadget/udc/core.c:1130: warning: Excess function parameter 'gadget' description in 'usb_gadget_udc_stop'
   drivers/usb/gadget/udc/core.c:1130: warning: Excess function parameter 'driver' description in 'usb_gadget_udc_stop'


vim +517 drivers/usb/gadget/udc/core.c

   508	
   509	/**
   510	 * usb_gsi_ep_op - performs operation on GSI accelerated EP based on EP op code
   511	 *
   512	 * Operations such as EP configuration, TRB allocation, StartXfer etc.
   513	 * See gsi_ep_op for more details.
   514	 */
   515	int usb_gsi_ep_op(struct usb_ep *ep,
   516			struct usb_gsi_request *req, enum gsi_ep_op op)
 > 517	{
   518		if (ep && ep->ops && ep->ops->gsi_ep_op)
   519			return ep->ops->gsi_ep_op(ep, req, op);
   520	
   521		return -EOPNOTSUPP;
   522	}
   523	EXPORT_SYMBOL_GPL(usb_gsi_ep_op);
   524	

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

                 reply	other threads:[~2024-12-12 12:22 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=202412122006.XUaCvCQa-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.