From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-6.1 7/7] drivers/usb/host/xhci-mem.c:391:16: sparse: sparse: Using plain integer as NULL pointer
Date: Tue, 24 Mar 2026 14:37:13 +0800 [thread overview]
Message-ID: <202603241400.14Ls3dsd-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android14-6.1
head: c0665c721df9b82c4652604d24aa91456058230b
commit: 90ab8e7f988d4bb2ceae033e4ea423e009459405 [7/7] ANDROID: usb: host: add xhci hooks for USB offload
config: arm64-randconfig-r122-20260324 (https://download.01.org/0day-ci/archive/20260324/202603241400.14Ls3dsd-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 10.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260324/202603241400.14Ls3dsd-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/202603241400.14Ls3dsd-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/usb/host/xhci-mem.c:391:16: sparse: sparse: Using plain integer as NULL pointer
drivers/usb/host/xhci-mem.c:1921:16: sparse: sparse: Using plain integer as NULL pointer
vim +391 drivers/usb/host/xhci-mem.c
381
382 static struct xhci_ring *xhci_vendor_alloc_transfer_ring(struct xhci_hcd *xhci,
383 u32 endpoint_type, enum xhci_ring_type ring_type,
384 unsigned int max_packet, gfp_t mem_flags)
385 {
386 struct xhci_vendor_ops *ops = xhci_vendor_get_ops(xhci);
387
388 if (ops && ops->alloc_transfer_ring)
389 return ops->alloc_transfer_ring(xhci, endpoint_type, ring_type,
390 max_packet, mem_flags);
> 391 return 0;
392 }
393
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-24 6:37 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=202603241400.14Ls3dsd-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.