From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 10929/12451] dtbs_check: Documentation/devicetree/bindings/mfd/qcom,tcsr.yaml:
Date: Tue, 17 Oct 2023 08:26:58 +0800 [thread overview]
Message-ID: <202310170810.1a8KESbb-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: Documentation/devicetree/bindings/mfd/qcom,tcsr.yaml:"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: Linux Memory Management List <linux-mm@kvack.org>
TO: Devi Priya <quic_devipriy@quicinc.com>
CC: Lee Jones <lee@kernel.org>
CC: Krzysztof Kozlowski <krzk@kernel.org>
CC: linux-doc@vger.kernel.org
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4d0515b235dec789578d135a5db586b25c5870cb
commit: b4a32d218d424b81a58fbd419e1114b1c1f76168 [10929/12451] dt-bindings: mfd: qcom,tcsr: Add simple-mfd support for IPQ6018
:::::: branch date: 19 hours ago
:::::: commit date: 5 days ago
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231017/202310170810.1a8KESbb-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/202310170810.1a8KESbb-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
Documentation/devicetree/bindings/mfd/qcom-pm8xxx.yaml:
Error in referenced schema matching $id: http://devicetree.org/schemas/input/qcom,pm8921-keypad.yaml
>> Documentation/devicetree/bindings/mfd/qcom,tcsr.yaml:
Error in referenced schema matching $id: http://devicetree.org/schemas/pwm/qcom,ipq6018-pwm.yaml
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-17 0:27 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=202310170810.1a8KESbb-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 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.