From: kernel test robot <lkp@intel.com>
To: Md Shofiqul Islam <shofiqtest@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, jic23@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
krzk@kernel.org, linux-kernel@vger.kernel.org,
Md Shofiqul Islam <shofiqtest@gmail.com>
Subject: Re: [PATCH] dt-bindings: iio: accel: Convert lis302 binding to YAML schema
Date: Thu, 11 Jun 2026 02:33:45 +0200 [thread overview]
Message-ID: <202606110223.IxhtwJBI-lkp@intel.com> (raw)
In-Reply-To: <20260610110051.1228-1-shofiqtest@gmail.com>
Hi Md,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on linus/master v7.1-rc7 next-20260610]
[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/Md-Shofiqul-Islam/dt-bindings-iio-accel-Convert-lis302-binding-to-YAML-schema/20260610-191419
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link: https://lore.kernel.org/r/20260610110051.1228-1-shofiqtest%40gmail.com
patch subject: [PATCH] dt-bindings: iio: accel: Convert lis302 binding to YAML schema
config: microblaze-randconfig-2052-20260610 (https://download.01.org/0day-ci/archive/20260611/202606110223.IxhtwJBI-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 15.2.0
dtschema: 2026.5.dev10+g5d839523d
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260611/202606110223.IxhtwJBI-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/202606110223.IxhtwJBI-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: Duplicate compatible "st,lis302dl-spi" found in schemas matching "$id":
http://devicetree.org/schemas/iio/accel/st,lis302dl.yaml
http://devicetree.org/schemas/iio/st,st-sensors.yaml#
>> Warning: Duplicate compatible "st,lis3lv02d" found in schemas matching "$id":
http://devicetree.org/schemas/iio/accel/st,lis302dl.yaml
http://devicetree.org/schemas/iio/st,st-sensors.yaml#
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-06-11 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 11:00 [PATCH] dt-bindings: iio: accel: Convert lis302 binding to YAML schema Md Shofiqul Islam
2026-06-10 11:16 ` sashiko-bot
2026-06-10 15:56 ` Jonathan Cameron
2026-06-10 16:40 ` Conor Dooley
2026-06-10 19:23 ` Rob Herring
2026-06-10 19:20 ` Rob Herring
2026-06-11 0:33 ` kernel test robot [this message]
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=202606110223.IxhtwJBI-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=shofiqtest@gmail.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