public inbox for oe-kbuild@lists.linux.dev
 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 v4 3/9] regulator: dt-bindings: Add MediaTek MT6392 PMIC
Date: Thu, 2 Apr 2026 08:54:51 +0200	[thread overview]
Message-ID: <202604020837.KM182aX5-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: <20260330083429.359819-4-l.scorcia@gmail.com>
References: <20260330083429.359819-4-l.scorcia@gmail.com>
TO: Luca Leonardo Scorcia <l.scorcia@gmail.com>
TO: linux-mediatek@lists.infradead.org
CC: Luca Leonardo Scorcia <l.scorcia@gmail.com>
CC: Dmitry Torokhov <dmitry.torokhov@gmail.com>
CC: Rob Herring <robh@kernel.org>
CC: Krzysztof Kozlowski <krzk@kernel.org>
CC: Conor Dooley <conor+dt@kernel.org>
CC: Sen Chu <sen.chu@mediatek.com>
CC: Sean Wang <sean.wang@mediatek.com>
CC: Macpaul Lin <macpaul.lin@mediatek.com>
CC: Lee Jones <lee@kernel.org>
CC: Matthias Brugger <matthias.bgg@gmail.com>
CC: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
CC: Linus Walleij <linusw@kernel.org>
CC: Liam Girdwood <lgirdwood@gmail.com>
CC: Mark Brown <broonie@kernel.org>
CC: Julien Massot <julien.massot@collabora.com>
CC: Gary Bisson <bisson.gary@gmail.com>
CC: "Louis-Alexis Eyraud" <louisalexis.eyraud@collabora.com>
CC: Val Packett <val@packett.cool>
CC: Fabien Parent <parent.f@gmail.com>
CC: Chen Zhong <chen.zhong@mediatek.com>
CC: linux-input@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: linux-pm@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: linux-gpio@vger.kernel.org

Hi Luca,

kernel test robot noticed the following build warnings:

[auto build test WARNING on lee-mfd/for-mfd-next]
[also build test WARNING on broonie-regulator/for-next linusw-pinctrl/devel linusw-pinctrl/for-next lee-mfd/for-mfd-fixes linus/master v7.0-rc6 next-20260401]
[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/Luca-Leonardo-Scorcia/dt-bindings-mfd-mt6397-Add-MT6392-PMIC/20260331-081127
base:   https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
patch link:    https://lore.kernel.org/r/20260330083429.359819-4-l.scorcia%40gmail.com
patch subject: [PATCH v4 3/9] regulator: dt-bindings: Add MediaTek MT6392 PMIC
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: arm-randconfig-2051-20260331 (https://download.01.org/0day-ci/archive/20260402/202604020837.KM182aX5-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.1.0
dtschema: 2025.13.dev11+ged7697fd8
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260402/202604020837.KM182aX5-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/202604020837.KM182aX5-lkp@intel.com/

dtcheck warnings: (new ones prefixed by >>)
   Documentation/devicetree/bindings/mfd/fsl,imx25-tsadc.yaml: Unresolvable reference: /schemas/input/touchscreen/fsl,imx25-tcq.yaml
>> Documentation/devicetree/bindings/regulator/mediatek,mt6392-regulator.yaml: 'maintainers' is a required property
   	hint: Metaschema for devicetree binding documentation
   	from schema $id: http://devicetree.org/meta-schemas/base.yaml
   Documentation/devicetree/bindings/mfd/maxim,max77620.yaml: Unresolvable reference: /schemas/pinctrl/maxim,max77620-pinctrl.yaml

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

                 reply	other threads:[~2026-04-02  6:55 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=202604020837.KM182aX5-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox