All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v2 06/15] dt-bindings: PCI: renesas,r9a08g045s33-pcie: Document RZ/G3E SoC
Date: Sat, 24 Jan 2026 07:46:16 +0100	[thread overview]
Message-ID: <202601240738.fJHaTFsU-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "dtcheck: binding changes may go via different trees"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260123140031.94752-7-john.madieu.xa@bp.renesas.com>
References: <20260123140031.94752-7-john.madieu.xa@bp.renesas.com>
TO: John Madieu <john.madieu.xa@bp.renesas.com>
TO: claudiu.beznea.uj@bp.renesas.com
TO: lpieralisi@kernel.org
TO: kwilczynski@kernel.org
TO: mani@kernel.org
TO: geert+renesas@glider.be
TO: krzk+dt@kernel.org
CC: robh@kernel.org
CC: bhelgaas@google.com
CC: conor+dt@kernel.org
CC: magnus.damm@gmail.com
CC: biju.das.jz@bp.renesas.com
CC: linux-pci@vger.kernel.org
CC: linux-renesas-soc@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-clk@vger.kernel.org
CC: john.madieu@gmail.com
CC: John Madieu <john.madieu.xa@bp.renesas.com>

Hi John,

kernel test robot noticed the following build warnings:

[auto build test WARNING on next-20260122]
[also build test WARNING on v6.19-rc6]
[cannot apply to pci/next pci/for-linus geert-renesas-drivers/renesas-clk geert-renesas-devel/next linus/master v6.19-rc6 v6.19-rc5 v6.19-rc4]
[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/John-Madieu/PCI-rzg3s-host-Fix-reset-handling-in-probe-error-path/20260123-220948
base:   next-20260122
patch link:    https://lore.kernel.org/r/20260123140031.94752-7-john.madieu.xa%40bp.renesas.com
patch subject: [PATCH v2 06/15] dt-bindings: PCI: renesas,r9a08g045s33-pcie: Document RZ/G3E SoC
:::::: branch date: 17 hours ago
:::::: commit date: 17 hours ago
config: microblaze-randconfig-2051-20260124 (https://download.01.org/0day-ci/archive/20260124/202601240738.fJHaTFsU-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 9.5.0
dtschema version: 2025.13.dev4+g85cec3155
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260124/202601240738.fJHaTFsU-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/202601240738.fJHaTFsU-lkp@intel.com/

dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/pci/renesas,r9a08g045-pcie.yaml: properties:reset-names: {'minItems': 1, 'maxItems': 7, 'items': [{'const': 'aresetn'}, {'const': 'rst_b'}, {'const': 'rst_gp_b'}, {'const': 'rst_ps_b'}, {'const': 'rst_rsm_b'}, {'const': 'rst_cfg_b'}, {'const': 'rst_load_b'}]} should not be valid under {'required': ['maxItems']}
   	hint: "maxItems" is not needed with an "items" list
   	from schema $id: http://devicetree.org/meta-schemas/items.yaml

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

             reply	other threads:[~2026-01-24  6:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-24  6:46 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-23 14:00 [PATCH v2 00/15] PCI: renesas: Add RZ/G3E PCIe controller support John Madieu
2026-01-23 14:00 ` [PATCH v2 06/15] dt-bindings: PCI: renesas,r9a08g045s33-pcie: Document RZ/G3E SoC John Madieu
2026-01-23 14:22   ` Biju Das
2026-01-23 15:16     ` John Madieu
2026-01-23 15:38   ` Rob Herring (Arm)
2026-01-26 14:31   ` Rob Herring
2026-01-26 16:46     ` John Madieu
2026-01-26 16:55       ` Biju Das

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=202601240738.fJHaTFsU-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.