devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ayush Singh <ayushdevel1325@gmail.com>, greybus-dev@lists.linaro.org
Cc: oe-kbuild-all@lists.linux.dev,
	Ayush Singh <ayushdevel1325@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org, vaishnav@beagleboard.org,
	jkridner@beagleboard.org, nm@ti.com,
	krzysztof.kozlowski+dt@linaro.org, vigneshr@ti.com,
	kristo@kernel.org, robh+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v9 1/3] dt-bindings: net: Add ti,cc1352p7
Date: Thu, 26 Oct 2023 22:00:01 +0800	[thread overview]
Message-ID: <202310262150.cA8h8EiZ-lkp@intel.com> (raw)
In-Reply-To: <20231017101116.178041-2-ayushdevel1325@gmail.com>

Hi Ayush,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 6269320850097903b30be8f07a5c61d9f7592393]

url:    https://github.com/intel-lab-lkp/linux/commits/Ayush-Singh/dt-bindings-net-Add-ti-cc1352p7/20231017-181305
base:   6269320850097903b30be8f07a5c61d9f7592393
patch link:    https://lore.kernel.org/r/20231017101116.178041-2-ayushdevel1325%40gmail.com
patch subject: [PATCH v9 1/3] dt-bindings: net: Add ti,cc1352p7
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231026/202310262150.cA8h8EiZ-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/202310262150.cA8h8EiZ-lkp@intel.com/

dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml:70:27: [error] string value is redundantly quoted with any quotes (quoted-strings)
   Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml:71:28: [error] string value is redundantly quoted with any quotes (quoted-strings)

vim +70 Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml

fbc00b5e746f13 Liang Yang      2022-09-07   8  
fbc00b5e746f13 Liang Yang      2022-09-07   9  allOf:
fbc00b5e746f13 Liang Yang      2022-09-07  10    - $ref: nand-controller.yaml
fbc00b5e746f13 Liang Yang      2022-09-07  11  
fbc00b5e746f13 Liang Yang      2022-09-07  12  maintainers:
fbc00b5e746f13 Liang Yang      2022-09-07  13    - liang.yang@amlogic.com
fbc00b5e746f13 Liang Yang      2022-09-07  14  
fbc00b5e746f13 Liang Yang      2022-09-07  15  properties:
fbc00b5e746f13 Liang Yang      2022-09-07  16    compatible:
fbc00b5e746f13 Liang Yang      2022-09-07  17      enum:
fbc00b5e746f13 Liang Yang      2022-09-07  18        - amlogic,meson-gxl-nfc
fbc00b5e746f13 Liang Yang      2022-09-07  19        - amlogic,meson-axg-nfc
fbc00b5e746f13 Liang Yang      2022-09-07  20  
fbc00b5e746f13 Liang Yang      2022-09-07  21    reg:
fbc00b5e746f13 Liang Yang      2022-09-07  22      maxItems: 2
fbc00b5e746f13 Liang Yang      2022-09-07  23  
fbc00b5e746f13 Liang Yang      2022-09-07  24    reg-names:
fbc00b5e746f13 Liang Yang      2022-09-07  25      items:
fbc00b5e746f13 Liang Yang      2022-09-07  26        - const: nfc
fbc00b5e746f13 Liang Yang      2022-09-07  27        - const: emmc
fbc00b5e746f13 Liang Yang      2022-09-07  28  
fbc00b5e746f13 Liang Yang      2022-09-07  29    interrupts:
fbc00b5e746f13 Liang Yang      2022-09-07  30      maxItems: 1
fbc00b5e746f13 Liang Yang      2022-09-07  31  
fbc00b5e746f13 Liang Yang      2022-09-07  32    clocks:
fbc00b5e746f13 Liang Yang      2022-09-07  33      minItems: 2
fbc00b5e746f13 Liang Yang      2022-09-07  34  
fbc00b5e746f13 Liang Yang      2022-09-07  35    clock-names:
fbc00b5e746f13 Liang Yang      2022-09-07  36      items:
fbc00b5e746f13 Liang Yang      2022-09-07  37        - const: core
fbc00b5e746f13 Liang Yang      2022-09-07  38        - const: device
fbc00b5e746f13 Liang Yang      2022-09-07  39  
fbc00b5e746f13 Liang Yang      2022-09-07  40  patternProperties:
fbc00b5e746f13 Liang Yang      2022-09-07  41    "^nand@[0-7]$":
fbc00b5e746f13 Liang Yang      2022-09-07  42      type: object
e37eaf5ebc5be6 Miquel Raynal   2023-06-19  43      $ref: raw-nand-chip.yaml
fbc00b5e746f13 Liang Yang      2022-09-07  44      properties:
fbc00b5e746f13 Liang Yang      2022-09-07  45        reg:
fbc00b5e746f13 Liang Yang      2022-09-07  46          minimum: 0
fbc00b5e746f13 Liang Yang      2022-09-07  47          maximum: 1
fbc00b5e746f13 Liang Yang      2022-09-07  48  
fbc00b5e746f13 Liang Yang      2022-09-07  49        nand-ecc-mode:
fbc00b5e746f13 Liang Yang      2022-09-07  50          const: hw
fbc00b5e746f13 Liang Yang      2022-09-07  51  
fbc00b5e746f13 Liang Yang      2022-09-07  52        nand-ecc-step-size:
c3519aed2a3faf Arseniy Krasnov 2023-07-11  53          enum: [512, 1024]
fbc00b5e746f13 Liang Yang      2022-09-07  54  
fbc00b5e746f13 Liang Yang      2022-09-07  55        nand-ecc-strength:
fbc00b5e746f13 Liang Yang      2022-09-07  56          enum: [8, 16, 24, 30, 40, 50, 60]
fbc00b5e746f13 Liang Yang      2022-09-07  57          description: |
fbc00b5e746f13 Liang Yang      2022-09-07  58            The ECC configurations that can be supported are as follows.
fbc00b5e746f13 Liang Yang      2022-09-07  59              meson-gxl-nfc 8, 16, 24, 30, 40, 50, 60
fbc00b5e746f13 Liang Yang      2022-09-07  60              meson-axg-nfc 8
fbc00b5e746f13 Liang Yang      2022-09-07  61  
262bc0096b7c91 Arseniy Krasnov 2023-06-08  62        nand-rb:
262bc0096b7c91 Arseniy Krasnov 2023-06-08  63          maxItems: 1
262bc0096b7c91 Arseniy Krasnov 2023-06-08  64          items:
262bc0096b7c91 Arseniy Krasnov 2023-06-08  65            maximum: 0
262bc0096b7c91 Arseniy Krasnov 2023-06-08  66  
e37eaf5ebc5be6 Miquel Raynal   2023-06-19  67      unevaluatedProperties: false
e37eaf5ebc5be6 Miquel Raynal   2023-06-19  68  
350301a3d73b21 Arseniy Krasnov 2023-07-17  69      dependencies:
350301a3d73b21 Arseniy Krasnov 2023-07-17 @70        nand-ecc-strength: ['nand-ecc-step-size']
350301a3d73b21 Arseniy Krasnov 2023-07-17  71        nand-ecc-step-size: ['nand-ecc-strength']
350301a3d73b21 Arseniy Krasnov 2023-07-17  72  
e37eaf5ebc5be6 Miquel Raynal   2023-06-19  73  
fbc00b5e746f13 Liang Yang      2022-09-07  74  required:
fbc00b5e746f13 Liang Yang      2022-09-07  75    - compatible
fbc00b5e746f13 Liang Yang      2022-09-07  76    - reg
fbc00b5e746f13 Liang Yang      2022-09-07  77    - interrupts
fbc00b5e746f13 Liang Yang      2022-09-07  78    - clocks
fbc00b5e746f13 Liang Yang      2022-09-07  79    - clock-names
fbc00b5e746f13 Liang Yang      2022-09-07  80  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-10-26 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 10:11 [PATCH v9 0/3] greybus: Add BeaglePlay Greybus Driver Ayush Singh
2023-10-17 10:11 ` [PATCH v9 1/3] dt-bindings: net: Add ti,cc1352p7 Ayush Singh
2023-10-26 14:00   ` kernel test robot [this message]
2023-10-17 10:11 ` [PATCH v9 2/3] greybus: Add BeaglePlay Linux Driver Ayush Singh
2023-10-17 10:11 ` [PATCH v9 3/3] dts: ti: k3-am625-beagleplay: Add beaglecc1352 Ayush Singh
2023-10-27 11:21 ` [PATCH v9 0/3] greybus: Add BeaglePlay Greybus Driver Greg KH

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=202310262150.cA8h8EiZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ayushdevel1325@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=jkridner@beagleboard.org \
    --cc=kristo@kernel.org \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=robh+dt@kernel.org \
    --cc=vaishnav@beagleboard.org \
    --cc=vigneshr@ti.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).