From: kernel test robot <lkp@intel.com>
To: Igor Prusov <ivprusov@salutedevices.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: oe-kbuild-all@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
kernel@salutedevices.com, prusovigor@gmail.com
Subject: Re: [PATCH v3 4/6] ASoC: codecs: Add NeoFidelity NTP8918 codec
Date: Fri, 27 Sep 2024 13:28:43 +0800 [thread overview]
Message-ID: <202409271307.H4zydYCv-lkp@intel.com> (raw)
In-Reply-To: <20240925-ntp-amps-8918-8835-v3-4-e2459a8191a6@salutedevices.com>
Hi Igor,
kernel test robot noticed the following build warnings:
[auto build test WARNING on c7fbbb45ef78ff349d16923b516bc8667367d1a6]
url: https://github.com/intel-lab-lkp/linux/commits/Igor-Prusov/dt-bindings-vendor-prefixes-Add-NeoFidelity-Inc/20240925-230818
base: c7fbbb45ef78ff349d16923b516bc8667367d1a6
patch link: https://lore.kernel.org/r/20240925-ntp-amps-8918-8835-v3-4-e2459a8191a6%40salutedevices.com
patch subject: [PATCH v3 4/6] ASoC: codecs: Add NeoFidelity NTP8918 codec
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
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/202409271307.H4zydYCv-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> sound/soc/codecs/ntp8918.c: linux/clk.h is included more than once.
vim +11 sound/soc/codecs/ntp8918.c
> 11 #include <linux/clk.h>
12 #include <linux/reset.h>
13 #include <linux/i2c.h>
14 #include <linux/regmap.h>
> 15 #include <linux/clk.h>
16 #include <linux/clk-provider.h>
17
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-27 5:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 14:52 [PATCH v3 0/6] ASoC: Add NTP8918 and NTP8835 codecs support Igor Prusov
2024-09-25 14:52 ` [PATCH v3 1/6] dt-bindings: vendor-prefixes: Add NeoFidelity, Inc Igor Prusov
2024-09-25 14:52 ` [PATCH v3 2/6] ASoC: codecs: Add NeoFidelity Firmware helpers Igor Prusov
2024-09-25 14:52 ` [PATCH v3 3/6] ASoC: dt-bindings: Add NeoFidelity NTP8918 Igor Prusov
2024-09-26 2:37 ` Rob Herring (Arm)
2024-09-25 14:52 ` [PATCH v3 4/6] ASoC: codecs: Add NeoFidelity NTP8918 codec Igor Prusov
2024-09-27 5:28 ` kernel test robot [this message]
2024-09-25 14:52 ` [PATCH v3 5/6] ASoC: dt-bindings: Add NeoFidelity NTP8835 Igor Prusov
2024-09-26 2:38 ` Rob Herring (Arm)
2024-09-25 14:52 ` [PATCH v3 6/6] ASoC: codecs: Add NeoFidelity NTP8835 codec Igor Prusov
2024-09-28 9:17 ` Dan Carpenter
2024-10-01 17:53 ` [PATCH v3 0/6] ASoC: Add NTP8918 and NTP8835 codecs support Mark Brown
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=202409271307.H4zydYCv-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=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).