From: kernel test robot <lkp@intel.com>
To: Xinhu Wu <xinhu.wu@unisoc.com>,
gregkh@linuxfoundation.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
orsonzhai@gmail.com, baolin.wang@linux.alibaba.com,
zhang.lyra@gmail.com, heikki.krogerus@linux.intel.com,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, xinhuwu.unisoc@gmail.com,
zhiyong.liu@unisoc.com, peak.yang@unisoc.com,
teng.zhang1@unisoc.com, bruce.chen@unisoc.com,
surong.pang@unisoc.com, xingxing.luo@unisoc.com,
xinhu.wu@unisoc.com
Subject: Re: [PATCH V2 2/2] dt-bindings: usb: Add an Spreadtrum pmic typec yaml
Date: Tue, 12 Dec 2023 03:35:57 +0800 [thread overview]
Message-ID: <202312120307.jhk5BElS-lkp@intel.com> (raw)
In-Reply-To: <20231211074120.27958-3-xinhu.wu@unisoc.com>
Hi Xinhu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on usb/usb-next usb/usb-linus robh/for-next westeri-thunderbolt/next linus/master v6.7-rc5 next-20231211]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Xinhu-Wu/usb-typec-Support-sprd_pmic_typec-driver/20231211-154328
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
patch link: https://lore.kernel.org/r/20231211074120.27958-3-xinhu.wu%40unisoc.com
patch subject: [PATCH V2 2/2] dt-bindings: usb: Add an Spreadtrum pmic typec yaml
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231212/202312120307.jhk5BElS-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/oe-kbuild-all/202312120307.jhk5BElS-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/usb/sprd,pmic_typec.yaml:28:18: [error] syntax error: mapping values are not allowed here (syntax)
--
>> Documentation/devicetree/bindings/usb/sprd,pmic_typec.yaml:28:18: mapping values are not allowed in this context
Documentation/devicetree/bindings/iio/pressure/honeywell,mprls0025pa.yaml: properties:honeywell,pmin-pascal: '$ref' should not be valid under {'const': '$ref'}
hint: Standard unit suffix properties don't need a type $ref
from schema $id: http://devicetree.org/meta-schemas/core.yaml#
Documentation/devicetree/bindings/iio/pressure/honeywell,mprls0025pa.yaml: properties:honeywell,pmax-pascal: '$ref' should not be valid under {'const': '$ref'}
hint: Standard unit suffix properties don't need a type $ref
from schema $id: http://devicetree.org/meta-schemas/core.yaml#
--
>> Documentation/devicetree/bindings/usb/sprd,pmic_typec.yaml: ignoring, error parsing file
vim +28 Documentation/devicetree/bindings/usb/sprd,pmic_typec.yaml
8
9 maintainers:
10 - Xinhu Wu <xinhu.wu@unisoc.com>
11
12 description:
13 Supports the typec found on these PMICs.
14
15 properties:
16 compatible:
17 enum:
18 - sprd,sc2730-typec
19
20 reg:
21 maxItems: 1
22
23 interrupts:
24 maxItems: 1
25
26 sprd,mode:
27 maxItems: 1
> 28 description: the number indicates src, snk or drp.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-12-11 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 7:41 [PATCH V2 0/2] usb: typec: sprd: Add Unisoc PMIC typec driver Xinhu Wu
2023-12-11 7:41 ` [PATCH V2 1/2] usb: typec: Support sprd_pmic_typec driver Xinhu Wu
2023-12-11 7:53 ` Greg KH
2023-12-11 17:35 ` Rob Herring
2023-12-11 18:51 ` kernel test robot
2023-12-11 19:11 ` kernel test robot
2023-12-11 7:41 ` [PATCH V2 2/2] dt-bindings: usb: Add an Spreadtrum pmic typec yaml Xinhu Wu
2023-12-11 8:20 ` Rob Herring
2023-12-11 19:35 ` kernel test robot [this message]
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=202312120307.jhk5BElS-lkp@intel.com \
--to=lkp@intel.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=bruce.chen@unisoc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=orsonzhai@gmail.com \
--cc=peak.yang@unisoc.com \
--cc=robh+dt@kernel.org \
--cc=surong.pang@unisoc.com \
--cc=teng.zhang1@unisoc.com \
--cc=xingxing.luo@unisoc.com \
--cc=xinhu.wu@unisoc.com \
--cc=xinhuwu.unisoc@gmail.com \
--cc=zhang.lyra@gmail.com \
--cc=zhiyong.liu@unisoc.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: 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).