From: kernel test robot <lkp@intel.com>
To: "Martin Povišer" <povik+lin@cutebit.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Hector Martin <marcan@marcan.st>
Subject: [asahilinux:bits/070-audio 6/33] sound/soc/codecs/tas2764.c:739:34: warning: array 'tas2764_of_match' assumed to have one element
Date: Fri, 23 Sep 2022 16:53:26 +0800 [thread overview]
Message-ID: <202209231658.cpB5WUql-lkp@intel.com> (raw)
tree: https://github.com/AsahiLinux/linux bits/070-audio
head: 5052d0fa99604a162270274e7a22a111862d824f
commit: 040ba7fbccbd82b839c15f7e80deb6dd58190be4 [6/33] ASoC: tas2764: Extend driver to SN012776
config: mips-randconfig-r013-20220922 (https://download.01.org/0day-ci/archive/20220923/202209231658.cpB5WUql-lkp@intel.com/config)
compiler: mipsel-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/AsahiLinux/linux/commit/040ba7fbccbd82b839c15f7e80deb6dd58190be4
git remote add asahilinux https://github.com/AsahiLinux/linux
git fetch --no-tags asahilinux bits/070-audio
git checkout 040ba7fbccbd82b839c15f7e80deb6dd58190be4
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash sound/soc/codecs/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> sound/soc/codecs/tas2764.c:739:34: warning: array 'tas2764_of_match' assumed to have one element
739 | static const struct of_device_id tas2764_of_match[];
| ^~~~~~~~~~~~~~~~
vim +/tas2764_of_match +739 sound/soc/codecs/tas2764.c
738
> 739 static const struct of_device_id tas2764_of_match[];
740
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-23 8:53 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=202209231658.cpB5WUql-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=povik+lin@cutebit.org \
/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