From: kernel test robot <lkp@intel.com>
To: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>,
linux-media@vger.kernel.org
Cc: kbuild-all@lists.01.org,
Dafna Hirschfeld <dafna.hirschfeld@collabora.com>,
Robert Beckett <bob.beckett@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
laurent.pinchart@ideasonboard.com, hverkuil@xs4all.nl,
kernel@collabora.com
Subject: Re: [PATCH v3 3/6] staging: media: wave5: Add the v4l2 layer
Date: Fri, 26 Nov 2021 13:10:45 +0800 [thread overview]
Message-ID: <202111261354.DVf9NPz7-lkp@intel.com> (raw)
In-Reply-To: <20211110120910.12411-4-dafna.hirschfeld@collabora.com>
Hi Dafna,
I love your patch! Perhaps something to improve:
[auto build test WARNING on staging/staging-testing]
url: https://github.com/0day-ci/linux/commits/Dafna-Hirschfeld/staging-media-wave5-add-wave5-codec-driver/20211110-201127
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git 8a893759d0075ea9556abcf86a4826d9865ba4bf
config: nios2-randconfig-s031-20211115 (https://download.01.org/0day-ci/archive/20211126/202111261354.DVf9NPz7-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/2fcd7c429c9a940f0e22894189556dfda264f127
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Dafna-Hirschfeld/staging-media-wave5-add-wave5-codec-driver/20211110-201127
git checkout 2fcd7c429c9a940f0e22894189556dfda264f127
# save the config file to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=nios2 SHELL=/bin/bash drivers/nvme/target/ drivers/staging/media/wave5/
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/staging/media/wave5/wave5-hw.c: note: in included file (through drivers/staging/media/wave5/vpu.h):
>> drivers/staging/media/wave5/vpuapi.h:842:29: sparse: sparse: dubious one-bit signed bitfield
--
drivers/staging/media/wave5/vpu.c: note: in included file (through drivers/staging/media/wave5/vpu.h):
>> drivers/staging/media/wave5/vpuapi.h:842:29: sparse: sparse: dubious one-bit signed bitfield
--
drivers/staging/media/wave5/vpuapi.c: note: in included file:
>> drivers/staging/media/wave5/vpuapi.h:842:29: sparse: sparse: dubious one-bit signed bitfield
--
drivers/staging/media/wave5/vdi.c: note: in included file (through drivers/staging/media/wave5/vpu.h):
>> drivers/staging/media/wave5/vpuapi.h:842:29: sparse: sparse: dubious one-bit signed bitfield
--
drivers/staging/media/wave5/vpu_enc.c: note: in included file (through drivers/staging/media/wave5/vpu.h):
>> drivers/staging/media/wave5/vpuapi.h:842:29: sparse: sparse: dubious one-bit signed bitfield
drivers/staging/media/wave5/vpu_enc.c: note: in included file:
>> drivers/staging/media/wave5/vpu.h:62:48: sparse: sparse: marked inline, but without a definition
>> drivers/staging/media/wave5/vpu.h:62:48: sparse: sparse: marked inline, but without a definition
--
drivers/staging/media/wave5/vpu_dec.c: note: in included file (through drivers/staging/media/wave5/vpu.h):
>> drivers/staging/media/wave5/vpuapi.h:842:29: sparse: sparse: dubious one-bit signed bitfield
drivers/staging/media/wave5/vpu_dec.c: note: in included file:
>> drivers/staging/media/wave5/vpu.h:62:48: sparse: sparse: marked inline, but without a definition
>> drivers/staging/media/wave5/vpu.h:62:48: sparse: sparse: marked inline, but without a definition
vim +62 drivers/staging/media/wave5/vpu.h
57
58 int wave5_vpu_dec_register_device(struct vpu_device *dev);
59 void wave5_vpu_dec_unregister_device(struct vpu_device *dev);
60 int wave5_vpu_enc_register_device(struct vpu_device *dev);
61 void wave5_vpu_enc_unregister_device(struct vpu_device *dev);
> 62 inline bool wave5_vpu_both_queues_are_streaming(struct vpu_instance *inst);
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-11-26 5:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 12:09 [PATCH v3 0/6] staging: media: wave5: add wave5 codec driver Dafna Hirschfeld
2021-11-10 12:09 ` [PATCH v3 1/6] staging: media: wave5: Add vpuapi layer Dafna Hirschfeld
2021-11-12 9:22 ` Dan Carpenter
2021-11-10 12:09 ` [PATCH v3 2/6] staging: media: wave5: Add the vdi layer Dafna Hirschfeld
2021-11-12 10:30 ` Dan Carpenter
2021-11-10 12:09 ` [PATCH v3 3/6] staging: media: wave5: Add the v4l2 layer Dafna Hirschfeld
2021-11-12 12:10 ` Dan Carpenter
2021-11-24 14:51 ` Dafna Hirschfeld
2021-11-26 5:10 ` kernel test robot [this message]
2021-11-27 3:04 ` Daniel Palmer
2021-11-10 12:09 ` [PATCH v3 4/6] staging: media: wave5: Add TODO file Dafna Hirschfeld
2021-11-10 12:09 ` [PATCH v3 5/6] dt-bindings: media: staging: wave5: add yaml devicetree bindings Dafna Hirschfeld
2021-11-10 12:09 ` [PATCH v3 6/6] media: wave5: Add wave5 driver to maintainers file Dafna Hirschfeld
2021-11-25 15:08 ` [PATCH v3 0/6] staging: media: wave5: add wave5 codec driver Hans Verkuil
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=202111261354.DVf9NPz7-lkp@intel.com \
--to=lkp@intel.com \
--cc=bob.beckett@collabora.com \
--cc=dafna.hirschfeld@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=kbuild-all@lists.01.org \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.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 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).