From: kernel test robot <philip.li@intel.com>
To: Emil Renner Berthing <kernel@esmil.dk>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-doc@vger.kernel.org>
Subject: [esmil:visionfive 20/46] dtbs_check: Documentation/devicetree/bindings/reset/starfive,jh7100-audrst.yaml: title: 'StarFive JH7100 SoC Audio Reset Controller Device Tree Bindings' should not be valid under {'pattern': '([Bb]inding| [Ss]chema)'}
Date: Wed, 27 Sep 2023 21:49:44 +0800 [thread overview]
Message-ID: <ZRQy+OkfOTL2tukm@rli9-mobl> (raw)
tree: https://github.com/esmil/linux visionfive
head: c727f594ac6d4d500eed929fe3bb1d6d90880662
commit: 15231f4e8cf50e957fc6e63586d34329f450ddcd [20/46] dt-bindings: reset: Add starfive,jh7100-audrst bindings
:::::: branch date: 2 days ago
:::::: commit date: 6 days ago
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230927/202309270130.Rq2jLCUA-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/202309270130.Rq2jLCUA-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/reset/starfive,jh7100-audrst.yaml: title: 'StarFive JH7100 SoC Audio Reset Controller Device Tree Bindings' should not be valid under {'pattern': '([Bb]inding| [Ss]chema)'}
hint: Everything is a binding/schema, no need to say it. Describe what hardware the binding is for.
from schema $id: http://devicetree.org/meta-schemas/base.yaml#
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-27 13:50 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=ZRQy+OkfOTL2tukm@rli9-mobl \
--to=philip.li@intel.com \
--cc=kernel@esmil.dk \
--cc=linux-doc@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox