From: kernel test robot <lkp@intel.com>
To: Neo Chang <YLCHANG2@nuvoton.com>
Cc: oe-kbuild-all@lists.linux.dev, Mark Brown <broonie@kernel.org>
Subject: [broonie-sound:for-next 20/61] sound/soc/codecs/nau8360-dsp.c:23:22: sparse: sparse: symbol 'nau8360_dsp_addr' was not declared. Should it be static?
Date: Wed, 02 Sep 2026 12:02:46 +0800 [thread overview]
Message-ID: <202609021121.a4mHPAyZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
head: 27a50351cbc82e9f0811df417c5e7d2a72f60ef5
commit: be88847a8bb1a14194cf50116f8909d127861318 [20/61] ASoC: codecs: nau8360: Add support for NAU83G60 amplifier
config: microblaze-randconfig-r133-20260902 (https://download.01.org/0day-ci/archive/20260902/202609021121.a4mHPAyZ-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 16.1.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260902/202609021121.a4mHPAyZ-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/202609021121.a4mHPAyZ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> sound/soc/codecs/nau8360-dsp.c:23:22: sparse: sparse: symbol 'nau8360_dsp_addr' was not declared. Should it be static?
--
>> sound/soc/codecs/nau8360.c:436:28: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned short [usertype] @@ got restricted __be16 [usertype] @@
sound/soc/codecs/nau8360.c:436:28: sparse: expected unsigned short [usertype]
sound/soc/codecs/nau8360.c:436:28: sparse: got restricted __be16 [usertype]
vim +/nau8360_dsp_addr +23 sound/soc/codecs/nau8360-dsp.c
21
22 #define NAU8360_DSP_IDLE_RETRY 10
> 23 const unsigned short nau8360_dsp_addr[NAU8360_DSP_FW_NUM] = {
24 NAU8360_RF000_DSP_COMM, NAU8360_RF002_DSP_COMM };
25
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-02 4:03 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=202609021121.a4mHPAyZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=YLCHANG2@nuvoton.com \
--cc=broonie@kernel.org \
--cc=oe-kbuild-all@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.