All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Valerio Setti <vsetti@baylibre.com>
Cc: oe-kbuild-all@lists.linux.dev, Mark Brown <broonie@kernel.org>,
	Jerome Brunet <jbrunet@baylibre.com>
Subject: [linux-next:master 1303/13846] sound/soc/meson/aiu.c:184:34: sparse: sparse: symbol 'aiu_formatter_i2s_drv' was not declared. Should it be static?
Date: Sat, 08 Aug 2026 07:00:48 +0800	[thread overview]
Message-ID: <202608080634.hf6aJGPB-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   6b8c8af514d739d0335f5579b585e02babe8a727
commit: 83b83024cdbfdddee104f4a84c2c2f1f8e6659f3 [1303/13846] ASoC: meson: aiu: use aiu-formatter-i2s to format I2S output data
config: nios2-randconfig-r122-20260807 (https://download.01.org/0day-ci/archive/20260808/202608080634.hf6aJGPB-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260808/202608080634.hf6aJGPB-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/202608080634.hf6aJGPB-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> sound/soc/meson/aiu.c:184:34: sparse: sparse: symbol 'aiu_formatter_i2s_drv' was not declared. Should it be static?

vim +/aiu_formatter_i2s_drv +184 sound/soc/meson/aiu.c

   183	
 > 184	const struct gx_formatter_driver aiu_formatter_i2s_drv = {
   185		.regmap_cfg	= &aiu_regmap_cfg,
   186		.ops		= &aiu_formatter_i2s_ops,
   187	};
   188	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-08-07 23:00 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=202608080634.hf6aJGPB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=broonie@kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=vsetti@baylibre.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 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.