From: kernel test robot <lkp@intel.com>
To: Igor Prusov <ivprusov@salutedevices.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
prusovigor@gmail.com, kernel@salutedevices.com,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] ASoC: codecs: Add NeoFidelity NTP8918 codec
Date: Thu, 11 Jul 2024 11:04:28 +0800 [thread overview]
Message-ID: <202407111044.RZFnMlVh-lkp@intel.com> (raw)
In-Reply-To: <20240709172834.9785-5-ivprusov@salutedevices.com>
Hi Igor,
kernel test robot noticed the following build warnings:
[auto build test WARNING on broonie-sound/for-next]
[also build test WARNING on robh/for-next linus/master v6.10-rc7 next-20240710]
[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/Igor-Prusov/dt-bindings-vendor-prefixes-Add-NeoFidelity-Inc/20240710-145725
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
patch link: https://lore.kernel.org/r/20240709172834.9785-5-ivprusov%40salutedevices.com
patch subject: [PATCH 4/6] ASoC: codecs: Add NeoFidelity NTP8918 codec
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240711/202407111044.RZFnMlVh-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240711/202407111044.RZFnMlVh-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/202407111044.RZFnMlVh-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/codecs/ntpfw.c:14: warning: cannot understand function prototype: 'struct ntpfw_chunk '
vim +14 sound/soc/codecs/ntpfw.c
fa3c817751bfd3 Igor Prusov 2024-07-09 13
fa3c817751bfd3 Igor Prusov 2024-07-09 @14 struct ntpfw_chunk {
fa3c817751bfd3 Igor Prusov 2024-07-09 15 __be16 length;
fa3c817751bfd3 Igor Prusov 2024-07-09 16 u8 step;
fa3c817751bfd3 Igor Prusov 2024-07-09 17 u8 data[];
fa3c817751bfd3 Igor Prusov 2024-07-09 18 } __packed;
fa3c817751bfd3 Igor Prusov 2024-07-09 19
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-07-11 3:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 17:28 [PATCH 0/6] ASoC: Add NTP8918 and NTP8835 codecs support Igor Prusov
2024-07-09 17:28 ` [PATCH 1/6] dt-bindings: vendor-prefixes: Add NeoFidelity, Inc Igor Prusov
2024-07-10 10:21 ` Krzysztof Kozlowski
2024-07-09 17:28 ` [PATCH 2/6] ASoC: codecs: Add NeoFidelity Firmware helpers Igor Prusov
2024-07-09 17:28 ` [PATCH 3/6] ASoC: dt-bindings: Add bindings for NeoFidelity NTP8918 Igor Prusov
2024-07-09 21:22 ` Rob Herring (Arm)
2024-07-10 10:23 ` Krzysztof Kozlowski
2024-07-09 17:28 ` [PATCH 4/6] ASoC: codecs: Add NeoFidelity NTP8918 codec Igor Prusov
2024-07-11 3:04 ` kernel test robot [this message]
2024-07-12 21:18 ` kernel test robot
2024-07-09 17:28 ` [PATCH 5/6] ASoC: dt-bindings: Add bindings for NeoFidelity NTP8835 Igor Prusov
2024-07-09 21:22 ` Rob Herring (Arm)
2024-07-10 10:24 ` Krzysztof Kozlowski
2024-09-20 17:42 ` Igor Prusov
2024-09-21 18:05 ` Krzysztof Kozlowski
2024-07-09 17:28 ` [PATCH 6/6] ASoC: codecs: Add NeoFidelity NTP8835 codec Igor Prusov
2024-07-10 10:31 ` Krzysztof Kozlowski
2024-09-20 17:33 ` Igor Prusov
2024-09-21 18:09 ` 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=202407111044.RZFnMlVh-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ivprusov@salutedevices.com \
--cc=kernel@salutedevices.com \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=p.zabel@pengutronix.de \
--cc=perex@perex.cz \
--cc=prusovigor@gmail.com \
--cc=robh@kernel.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).