From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v2 1/1] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561
Date: Thu, 8 Aug 2024 13:27:57 +0800 [thread overview]
Message-ID: <202408081330.78WSlgKc-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: <20240807180956.1341332-2-ilordash02@gmail.com>
References: <20240807180956.1341332-2-ilordash02@gmail.com>
TO: Ilya Orazov <ilordash02@gmail.com>
TO: "Marc Kleine-Budde" <mkl@pengutronix.de>
TO: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
TO: Vinod Koul <vkoul@kernel.org>
TO: Kishon Vijay Abraham I <kishon@kernel.org>
TO: Rob Herring <robh@kernel.org>
TO: Krzysztof Kozlowski <krzk@kernel.org>
TO: Aswath Govindraju <a-govindraju@ti.com>
TO: Conor Dooley <conor+dt@kernel.org>
CC: linux-can@vger.kernel.org
CC: linux-phy@lists.infradead.org
CC: devicetree@vger.kernel.org
CC: Ilya Orazov <ilordash02@gmail.com>
Hi Ilya,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mkl-can-next/testing]
[also build test WARNING on linus/master v6.11-rc2 next-20240807]
[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/Ilya-Orazov/dt-bindings-phy-ti-tcan104x-can-Document-Microchip-ATA6561/20240808-045713
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git testing
patch link: https://lore.kernel.org/r/20240807180956.1341332-2-ilordash02%40gmail.com
patch subject: [PATCH v2 1/1] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561
:::::: branch date: 8 hours ago
:::::: commit date: 8 hours ago
config: arc-randconfig-051-20240808 (https://download.01.org/0day-ci/archive/20240808/202408081330.78WSlgKc-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
dtschema version: 2024.6.dev8+gf13c181
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240808/202408081330.78WSlgKc-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/202408081330.78WSlgKc-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml: ignoring, error parsing file
Documentation/devicetree/bindings/net/snps,dwmac.yaml: mac-mode: missing type definition
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-08-08 5:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 5:27 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-05 10:11 [PATCH 1/2] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561 Conor Dooley
2024-08-07 18:02 ` [PATCH v2 0/1] phy: Add support for Microchip ATA6561 CAN Transceiver Ilya Orazov
2024-08-07 18:02 ` [PATCH v2 1/1] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561 Ilya Orazov
2024-08-07 18:02 ` Ilya Orazov
2024-08-07 18:09 ` [PATCH v2 0/1] phy: Add support for Microchip ATA6561 CAN Transceiver Ilya Orazov
2024-08-07 18:09 ` [PATCH v2 1/1] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561 Ilya Orazov
2024-08-07 18:09 ` Ilya Orazov
2024-08-07 19:12 ` Rob Herring (Arm)
2024-08-07 19:12 ` Rob Herring (Arm)
2024-08-08 15:48 ` Conor Dooley
2024-08-08 15:48 ` Conor Dooley
2024-08-08 16:40 ` Krzysztof Kozlowski
2024-08-08 16:40 ` Krzysztof Kozlowski
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=202408081330.78WSlgKc-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.