From: kernel test robot <lkp@intel.com>
To: “Ryan <ryan.lee.analog@gmail.com>,
lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, perex@perex.cz,
tiwai@suse.com, rf@opensource.cirrus.com, ryans.lee@analog.com,
wangweidong.a@awinic.com, shumingf@realtek.com,
herve.codina@bootlin.com, ckeepax@opensource.cirrus.com,
doug@schmorgal.com, ajye_huang@compal.corp-partner.google.com,
kiseok.jo@irondevice.com, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, venkataprasad.potturu@amd.com
Subject: Re: [PATCH 2/2] ASoC: max98388: add amplifier driver
Date: Thu, 8 Jun 2023 20:21:12 +0800 [thread overview]
Message-ID: <202306082054.jIU9oENf-lkp@intel.com> (raw)
In-Reply-To: <20230608054230.344014-2-ryan.lee.analog@gmail.com>
Hi “Ryan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on broonie-sound/for-next]
[also build test WARNING on linus/master v6.4-rc5 next-20230608]
[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/Ryan/ASoC-max98388-add-amplifier-driver/20230608-134526
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
patch link: https://lore.kernel.org/r/20230608054230.344014-2-ryan.lee.analog%40gmail.com
patch subject: [PATCH 2/2] ASoC: max98388: add amplifier driver
config: mips-allmodconfig (https://download.01.org/0day-ci/archive/20230608/202306082054.jIU9oENf-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 12.3.0
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add broonie-sound https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
git fetch broonie-sound for-next
git checkout broonie-sound/for-next
b4 shazam https://lore.kernel.org/r/20230608054230.344014-2-ryan.lee.analog@gmail.com
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=mips olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash sound/soc/codecs/
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/202306082054.jIU9oENf-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/codecs/max98388.c:390:6: warning: no previous prototype for 'max98388_reset' [-Wmissing-prototypes]
390 | void max98388_reset(struct max98388_priv *max98388, struct device *dev)
| ^~~~~~~~~~~~~~
>> sound/soc/codecs/max98388.c:904:6: warning: no previous prototype for 'max98388_read_deveice_property' [-Wmissing-prototypes]
904 | void max98388_read_deveice_property(struct device *dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/max98388_reset +390 sound/soc/codecs/max98388.c
389
> 390 void max98388_reset(struct max98388_priv *max98388, struct device *dev)
391 {
392 int ret, reg, count;
393
394 /* Software Reset */
395 ret = regmap_update_bits(max98388->regmap,
396 MAX98388_R2000_SW_RESET,
397 MAX98388_SOFT_RESET,
398 MAX98388_SOFT_RESET);
399 if (ret)
400 dev_err(dev, "Reset command failed. (ret:%d)\n", ret);
401
402 count = 0;
403 while (count < 3) {
404 usleep_range(10000, 11000);
405 /* Software Reset Verification */
406 ret = regmap_read(max98388->regmap,
407 MAX98388_R22FF_REV_ID, ®);
408 if (!ret) {
409 dev_info(dev, "Reset completed (retry:%d)\n", count);
410 return;
411 }
412 count++;
413 }
414 dev_err(dev, "Reset failed. (ret:%d)\n", ret);
415 }
416
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-08 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 5:42 [PATCH 1/2] ASoC: dt-bindings: max98388: add amplifier driver “Ryan
2023-06-08 5:42 ` [PATCH 2/2] ASoC: " “Ryan
2023-06-08 12:21 ` kernel test robot [this message]
2023-06-08 7:18 ` [PATCH 1/2] ASoC: dt-bindings: " Krzysztof Kozlowski
2023-06-09 23:52 ` Lee, RyanS
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=202306082054.jIU9oENf-lkp@intel.com \
--to=lkp@intel.com \
--cc=ajye_huang@compal.corp-partner.google.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=doug@schmorgal.com \
--cc=herve.codina@bootlin.com \
--cc=kiseok.jo@irondevice.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=robh+dt@kernel.org \
--cc=ryan.lee.analog@gmail.com \
--cc=ryans.lee@analog.com \
--cc=shumingf@realtek.com \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.com \
--cc=wangweidong.a@awinic.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).