From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 1933/3131] Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml:56: example 0 [redundant-whitespace] extra whitespace before {
Date: Thu, 03 Sep 2026 06:54:15 +0200 [thread overview]
Message-ID: <202609030635.eSuyzFSp-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check first_new_problem: Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml:56: example 0 [redundant-whitespace] extra whitespace before {"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Krzysztof Kozlowski <krzk@kernel.org>
CC: "Rob Herring (Arm)" <robh@kernel.org>
CC: linux-doc@vger.kernel.org
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 32b6ef9a5d0eca44f9cd91f52f4faa89f145a0de
commit: ed47943d94f18bb2ca2995936ae8c06f65fa720e [1933/3131] dtc: dt-check-style: Add warning for redundant white-spaces
:::::: branch date: 16 hours ago
:::::: commit date: 3 days ago
config: arc-randconfig-2051-20260902 (https://download.01.org/0day-ci/archive/20260903/202609030635.eSuyzFSp-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 12.5.0
dtschema: 2026.7.dev16+g39602f98e
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260903/202609030635.eSuyzFSp-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/r/202609030635.eSuyzFSp-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml:56: example 0 [redundant-whitespace] extra whitespace before {
vim +56 Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml
cbc775e060cecb Jacopo Mondi 2024-06-26 47
cbc775e060cecb Jacopo Mondi 2024-06-26 48 examples:
cbc775e060cecb Jacopo Mondi 2024-06-26 49 - |
cbc775e060cecb Jacopo Mondi 2024-06-26 50 #include <dt-bindings/interrupt-controller/arm-gic.h>
cbc775e060cecb Jacopo Mondi 2024-06-26 51
cbc775e060cecb Jacopo Mondi 2024-06-26 52 soc {
cbc775e060cecb Jacopo Mondi 2024-06-26 53 #address-cells = <2>;
cbc775e060cecb Jacopo Mondi 2024-06-26 54 #size-cells = <2>;
cbc775e060cecb Jacopo Mondi 2024-06-26 55
cbc775e060cecb Jacopo Mondi 2024-06-26 @56 isp@880000 {
:::::: The code at line 56 was first introduced by commit
:::::: cbc775e060cecbdb7210f46d8e7a65df2a865ee7 media: dt-bindings: Add bindings for Raspberry Pi PiSP Back End
:::::: TO: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
:::::: CC: Hans Verkuil <hverkuil-cisco@xs4all.nl>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-03 4:54 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=202609030635.eSuyzFSp-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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