From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] dt-bindings: sound: Convert pcm3060 to DT schema
Date: Fri, 3 Apr 2026 12:15:41 +0200 [thread overview]
Message-ID: <202604031208.j86jIMBW-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: <20260326153041.496811-1-padmashreess2006@gmail.com>
References: <20260326153041.496811-1-padmashreess2006@gmail.com>
TO: Padmashree S S <padmashreess2006@gmail.com>
TO: k.marinushkin@gmail.com
TO: lgirdwood@gmail.com
TO: broonie@kernel.org
CC: robh@kernel.org
CC: conor+dt@kernel.org
CC: krzk+dt@kernel.org
CC: linux-sound@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: Padmashree S S <padmashreess2006@gmail.com>
Hi Padmashree,
kernel test robot noticed the following build warnings:
[auto build test WARNING on broonie-sound/for-next]
[also build test WARNING on linus/master v7.0-rc6 next-20260402]
[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/Padmashree-S-S/dt-bindings-sound-Convert-pcm3060-to-DT-schema/20260329-162206
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
patch link: https://lore.kernel.org/r/20260326153041.496811-1-padmashreess2006%40gmail.com
patch subject: [PATCH] dt-bindings: sound: Convert pcm3060 to DT schema
:::::: branch date: 5 days ago
:::::: commit date: 5 days ago
config: arc-randconfig-2052-20260403 (https://download.01.org/0day-ci/archive/20260403/202604031208.j86jIMBW-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 8.5.0
dtschema: 2025.13.dev13+g7ce498b67
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260403/202604031208.j86jIMBW-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/202604031208.j86jIMBW-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/sound/pcm3060.yaml:45:7: [error] no new line character at the end of file (new-line-at-end-of-file)
Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.yaml:52:2: [warning] wrong indentation: expected 2 but found 1 (indentation)
Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.yaml:84:1: [warning] too many blank lines (2 > 1) (empty-lines)
vim +45 Documentation/devicetree/bindings/sound/pcm3060.yaml
39cbb0e557c64c Padmashree S S 2026-03-26 33
39cbb0e557c64c Padmashree S S 2026-03-26 34 examples:
39cbb0e557c64c Padmashree S S 2026-03-26 35 - |
39cbb0e557c64c Padmashree S S 2026-03-26 36 i2c {
39cbb0e557c64c Padmashree S S 2026-03-26 37 #address-cells = <1>;
39cbb0e557c64c Padmashree S S 2026-03-26 38 #size-cells = <0>;
39cbb0e557c64c Padmashree S S 2026-03-26 39
39cbb0e557c64c Padmashree S S 2026-03-26 40 pcm3060: audio-codec@46 {
39cbb0e557c64c Padmashree S S 2026-03-26 41 compatible = "ti,pcm3060";
39cbb0e557c64c Padmashree S S 2026-03-26 42 reg = <0x46>;
39cbb0e557c64c Padmashree S S 2026-03-26 43 ti,out-single-ended;
39cbb0e557c64c Padmashree S S 2026-03-26 44 };
39cbb0e557c64c Padmashree S S 2026-03-26 @45 };
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-03 10:16 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=202604031208.j86jIMBW-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