From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [ambarus:acpm-v3-upstream 7/10] Documentation/devicetree/bindings/firmware/samsung,exynos-acpm-ipc.yaml: ignoring, error parsing file
Date: Fri, 6 Dec 2024 00:29:02 +0800 [thread overview]
Message-ID: <202412060036.Bi6iiVnc-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
TO: Tudor Ambarus <tudor.ambarus@linaro.org>
CC: linux-doc@vger.kernel.org
tree: https://github.com/ambarus/linux-0day acpm-v3-upstream
head: 20f606fa2a40e27ec03a65c1a7e7d59617173b99
commit: 7bc94b457d841b0bd51c226ce6f8389e88bd88c7 [7/10] dt-bindings: firmware: add samsung,exynos-acpm-ipc bindings
:::::: branch date: 22 hours ago
:::::: commit date: 22 hours ago
config: arm-randconfig-052-20241205 (https://download.01.org/0day-ci/archive/20241206/202412060036.Bi6iiVnc-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
dtschema version: 2024.12.dev3+g93ee800
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241206/202412060036.Bi6iiVnc-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/202412060036.Bi6iiVnc-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/firmware/samsung,exynos-acpm-ipc.yaml: ignoring, error parsing file
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-05 16:29 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=202412060036.Bi6iiVnc-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.