From: kbuild test robot <lkp@intel.com> To: Maxime Chevallier <maxime.chevallier@bootlin.com>, Mauro Carvalho Chehab <mchehab@kernel.org>, Robin Murphy <robin.murphy@arm.com>, Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>, Heiko Stuebner <heiko@sntech.de>, Hans Verkuil <hverkuil@xs4all.nl> Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com, linux-media@vger.kernel.org, Maxime Chevallier <maxime.chevallier@bootlin.com>, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 2/3] media: rockchip: Introduce driver for Rockhip's camera interface Date: Sun, 31 May 2020 20:16:07 +0800 [thread overview] Message-ID: <202005312015.VQOP2NK6%lkp@intel.com> (raw) In-Reply-To: <20200529130405.929429-3-maxime.chevallier@bootlin.com> [-- Attachment #1: Type: text/plain, Size: 3247 bytes --] Hi Maxime, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linuxtv-media/master] [also build test WARNING on rockchip/for-next robh/for-next v5.7-rc7 next-20200529] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982] url: https://github.com/0day-ci/linux/commits/Maxime-Chevallier/media-rockchip-Introduce-driver-for-the-camera-interface-on-PX30/20200531-081952 base: git://linuxtv.org/media_tree.git master config: x86_64-allyesconfig (attached as .config) compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 2388a096e7865c043e83ece4e26654bd3d1a20d5) reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # install x86_64 cross compiling tool for clang build # apt-get install binutils-x86-64-linux-gnu # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 If you fix the issue, kindly add following tag as appropriate Reported-by: kbuild test robot <lkp@intel.com> All warnings (new ones prefixed by >>, old ones prefixed by <<): In file included from drivers/media/platform/rockchip/cif/dev.c:22: >> drivers/media/platform/rockchip/cif/regs.h:113:9: warning: 'FRAME_END' macro redefined [-Wmacro-redefined] #define FRAME_END (0x01 << 0) ^ arch/x86/include/asm/frame.h:89:9: note: previous definition is here #define FRAME_END ^ >> drivers/media/platform/rockchip/cif/dev.c:253:13: warning: variable 'v4l2_dev' is uninitialized when used here [-Wuninitialized] v4l2_info(v4l2_dev, "No reserved memory region assign to CIFn"); ^~~~~~~~ include/media/v4l2-common.h:67:25: note: expanded from macro 'v4l2_info' v4l2_printk(KERN_INFO, dev, fmt , ## arg) ^~~ include/media/v4l2-common.h:58:28: note: expanded from macro 'v4l2_printk' printk(level "%s: " fmt, (dev)->name , ## arg) ^~~ drivers/media/platform/rockchip/cif/dev.c:216:30: note: initialize the variable 'v4l2_dev' to silence this warning struct v4l2_device *v4l2_dev; ^ = NULL 2 warnings generated. -- In file included from drivers/media/platform/rockchip/cif/capture.c:22: >> drivers/media/platform/rockchip/cif/regs.h:113:9: warning: 'FRAME_END' macro redefined [-Wmacro-redefined] #define FRAME_END (0x01 << 0) ^ arch/x86/include/asm/frame.h:89:9: note: previous definition is here #define FRAME_END ^ 1 warning generated. vim +/FRAME_END +113 drivers/media/platform/rockchip/cif/regs.h 110 111 /* CIF INTSTAT */ 112 #define INTSTAT_CLS (0x3FF) > 113 #define FRAME_END (0x01 << 0) 114 #define LINE_ERR (0x01 << 2) 115 #define PST_INF_FRAME_END (0x01 << 9) 116 #define FRAME_END_CLR (0x01 << 0) 117 #define LINE_ERR_CLR (0x01 << 2) 118 #define PST_INF_FRAME_END_CLR (0x01 << 9) 119 #define INTSTAT_ERR (0xFC) 120 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org [-- Attachment #2: .config.gz --] [-- Type: application/gzip, Size: 73692 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH v2 2/3] media: rockchip: Introduce driver for Rockhip's camera interface Date: Sun, 31 May 2020 20:16:07 +0800 [thread overview] Message-ID: <202005312015.VQOP2NK6%lkp@intel.com> (raw) In-Reply-To: <20200529130405.929429-3-maxime.chevallier@bootlin.com> [-- Attachment #1: Type: text/plain, Size: 3322 bytes --] Hi Maxime, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linuxtv-media/master] [also build test WARNING on rockchip/for-next robh/for-next v5.7-rc7 next-20200529] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982] url: https://github.com/0day-ci/linux/commits/Maxime-Chevallier/media-rockchip-Introduce-driver-for-the-camera-interface-on-PX30/20200531-081952 base: git://linuxtv.org/media_tree.git master config: x86_64-allyesconfig (attached as .config) compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 2388a096e7865c043e83ece4e26654bd3d1a20d5) reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # install x86_64 cross compiling tool for clang build # apt-get install binutils-x86-64-linux-gnu # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 If you fix the issue, kindly add following tag as appropriate Reported-by: kbuild test robot <lkp@intel.com> All warnings (new ones prefixed by >>, old ones prefixed by <<): In file included from drivers/media/platform/rockchip/cif/dev.c:22: >> drivers/media/platform/rockchip/cif/regs.h:113:9: warning: 'FRAME_END' macro redefined [-Wmacro-redefined] #define FRAME_END (0x01 << 0) ^ arch/x86/include/asm/frame.h:89:9: note: previous definition is here #define FRAME_END ^ >> drivers/media/platform/rockchip/cif/dev.c:253:13: warning: variable 'v4l2_dev' is uninitialized when used here [-Wuninitialized] v4l2_info(v4l2_dev, "No reserved memory region assign to CIFn"); ^~~~~~~~ include/media/v4l2-common.h:67:25: note: expanded from macro 'v4l2_info' v4l2_printk(KERN_INFO, dev, fmt , ## arg) ^~~ include/media/v4l2-common.h:58:28: note: expanded from macro 'v4l2_printk' printk(level "%s: " fmt, (dev)->name , ## arg) ^~~ drivers/media/platform/rockchip/cif/dev.c:216:30: note: initialize the variable 'v4l2_dev' to silence this warning struct v4l2_device *v4l2_dev; ^ = NULL 2 warnings generated. -- In file included from drivers/media/platform/rockchip/cif/capture.c:22: >> drivers/media/platform/rockchip/cif/regs.h:113:9: warning: 'FRAME_END' macro redefined [-Wmacro-redefined] #define FRAME_END (0x01 << 0) ^ arch/x86/include/asm/frame.h:89:9: note: previous definition is here #define FRAME_END ^ 1 warning generated. vim +/FRAME_END +113 drivers/media/platform/rockchip/cif/regs.h 110 111 /* CIF INTSTAT */ 112 #define INTSTAT_CLS (0x3FF) > 113 #define FRAME_END (0x01 << 0) 114 #define LINE_ERR (0x01 << 2) 115 #define PST_INF_FRAME_END (0x01 << 9) 116 #define FRAME_END_CLR (0x01 << 0) 117 #define LINE_ERR_CLR (0x01 << 2) 118 #define PST_INF_FRAME_END_CLR (0x01 << 9) 119 #define INTSTAT_ERR (0xFC) 120 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org [-- Attachment #2: config.gz --] [-- Type: application/gzip, Size: 73692 bytes --]
next prev parent reply other threads:[~2020-05-31 13:03 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-29 13:04 [PATCH v2 0/3] media: rockchip: Introduce driver for the camera interface on PX30 Maxime Chevallier 2020-05-29 13:04 ` Maxime Chevallier 2020-05-29 13:04 ` Maxime Chevallier 2020-05-29 13:04 ` [PATCH v2 1/3] media: dt-bindings: media: Document Rockchip CIF bindings Maxime Chevallier 2020-05-29 13:04 ` Maxime Chevallier 2020-05-29 16:14 ` Rob Herring 2020-05-29 16:14 ` Rob Herring 2020-05-29 16:14 ` Rob Herring 2020-05-29 13:04 ` [PATCH v2 2/3] media: rockchip: Introduce driver for Rockhip's camera interface Maxime Chevallier 2020-05-29 13:04 ` Maxime Chevallier 2020-05-31 4:39 ` kbuild test robot 2020-05-31 4:39 ` kbuild test robot 2020-05-31 4:39 ` kbuild test robot 2020-05-31 12:16 ` kbuild test robot [this message] 2020-05-31 12:16 ` kbuild test robot 2020-05-31 13:40 ` Ezequiel Garcia 2020-05-31 13:40 ` Ezequiel Garcia 2020-07-09 7:35 ` Maxime Chevallier 2020-07-09 7:35 ` Maxime Chevallier 2020-07-09 7:35 ` Maxime Chevallier 2020-07-09 18:06 ` Dafna Hirschfeld 2020-07-09 18:06 ` Dafna Hirschfeld 2020-07-09 18:06 ` Dafna Hirschfeld 2020-05-29 13:04 ` [PATCH v2 3/3] arm64: dts: rockchip: Add the camera interface description of the PX30 Maxime Chevallier 2020-05-29 13:04 ` Maxime Chevallier 2020-06-01 18:45 ` [PATCH v2 0/3] media: rockchip: Introduce driver for the camera interface on PX30 Tomasz Figa 2020-06-01 18:45 ` Tomasz Figa 2020-06-01 21:38 ` Heiko Stübner 2020-06-04 17:04 ` Tomasz Figa
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=202005312015.VQOP2NK6%lkp@intel.com \ --to=lkp@intel.com \ --cc=clang-built-linux@googlegroups.com \ --cc=devicetree@vger.kernel.org \ --cc=heiko@sntech.de \ --cc=hverkuil@xs4all.nl \ --cc=kbuild-all@lists.01.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-media@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=maxime.chevallier@bootlin.com \ --cc=mchehab@kernel.org \ --cc=robh+dt@kernel.org \ --cc=robin.murphy@arm.com \ /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: linkBe 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.