From: kernel test robot <lkp@intel.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [mnyman-xhci:feature_interrupters 4/4] drivers/usb/host/xhci-sideband.c:244:66: error: too few arguments to function call, expected 2, have 1
Date: Tue, 30 Jan 2024 20:18:51 +0800 [thread overview]
Message-ID: <202401302024.R12VFof5-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git feature_interrupters
head: a7f098b5bba5fe24fe938751ed128c6dd9b967f9
commit: a7f098b5bba5fe24fe938751ed128c6dd9b967f9 [4/4] xhci: sideband: add initial api to register a sideband entity
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240130/202401302024.R12VFof5-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240130/202401302024.R12VFof5-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/202401302024.R12VFof5-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/usb/host/xhci-sideband.c:244:66: error: too few arguments to function call, expected 2, have 1
244 | sb->ir = xhci_create_secondary_interrupter(xhci_to_hcd(sb->xhci));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
drivers/usb/host/xhci.h:2093:1: note: 'xhci_create_secondary_interrupter' declared here
2093 | xhci_create_secondary_interrupter(struct usb_hcd *hcd, int num_seg);
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +244 drivers/usb/host/xhci-sideband.c
224
225 /**
226 * xhci_sideband_create_interrupter - creates a new interrupter for this sideband
227 * @sb: sideband instance for this usb device
228 *
229 * Sets up a xhci interrupter that can be used for this sideband accessed usb
230 * device. Transfer events for this device can be routed to this interrupters
231 * event ring by setting the 'Interrupter Target' field correctly when queueing
232 * the transfer TRBs.
233 * Once this interrupter is created the interrupter target ID can be obtained
234 * by calling xhci_sideband_interrupter_id()
235 *
236 * Returns 0 on success, negative error otherwise
237 */
238 int
239 xhci_sideband_create_interrupter(struct xhci_sideband *sb)
240 {
241 if (sb->ir)
242 return -EBUSY;
243
> 244 sb->ir = xhci_create_secondary_interrupter(xhci_to_hcd(sb->xhci));
245 if (!sb->ir)
246 return -ENOMEM;
247
248 return 0;
249 }
250
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-30 12:19 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=202401302024.R12VFof5-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mathias.nyman@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox