From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [rcar:vsp1/v3u 13/23] drivers/media/v4l2-core/v4l2-async.c:777:5: sparse: sparse: symbol 'v4l2_async_pending_devices' was not declared. Should it be
Date: Wed, 17 Mar 2021 23:57:32 +0800 [thread overview]
Message-ID: <202103172338.acvmDsR4-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kbingham/rcar.git vsp1/v3u
head: 178de9aa2b539612048856e54a292efda80f41c1
commit: fb68cc895bd671aa7d0b1cf67f873edb9b2a3f2e [13/23] WIP: Add async notifier state debug
config: x86_64-randconfig-s022-20210317 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-277-gc089cd2d-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/kbingham/rcar.git/commit/?id=fb68cc895bd671aa7d0b1cf67f873edb9b2a3f2e
git remote add rcar https://git.kernel.org/pub/scm/linux/kernel/git/kbingham/rcar.git
git fetch --no-tags rcar vsp1/v3u
git checkout fb68cc895bd671aa7d0b1cf67f873edb9b2a3f2e
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/media/v4l2-core/v4l2-async.c:777:5: sparse: sparse: symbol 'v4l2_async_pending_devices' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 38118 bytes --]
next reply other threads:[~2021-03-17 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 15:57 kernel test robot [this message]
2021-03-17 15:57 ` [RFC PATCH rcar] WIP: v4l2_async_pending_devices() can be static kernel test robot
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=202103172338.acvmDsR4-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.