From: kernel test robot <lkp@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [morimoto:sound-cleanup-2026-04-06 119/119] sound/soc/codecs/si476x.c:222:10: sparse: sparse: Initializer entry defined twice
Date: Tue, 07 Apr 2026 21:14:05 +0800 [thread overview]
Message-ID: <202604072139.9CeDasUz-lkp@intel.com> (raw)
tree: https://github.com/morimoto/linux sound-cleanup-2026-04-06
head: 557e71769b656376e9a03618f6e770bb6a3defd5
commit: 29d2324ae7f721e5087e6b950a20d953b0c71cf2 [119/119] hoge
config: x86_64-randconfig-121-20260407 (https://download.01.org/0day-ci/archive/20260407/202604072139.9CeDasUz-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260407/202604072139.9CeDasUz-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/202604072139.9CeDasUz-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> sound/soc/codecs/si476x.c:222:10: sparse: sparse: Initializer entry defined twice
sound/soc/codecs/si476x.c:224:10: sparse: also defined here
vim +222 sound/soc/codecs/si476x.c
218
219 static const struct snd_soc_dai_ops si476x_dai_ops = {
220 .hw_params = si476x_codec_hw_params,
221 .set_fmt = si476x_codec_set_dai_fmt,
> 222 .num_auto_selectable_formats = 1,
223 .auto_selectable_formats = ssm3515_selectable_formats,
224 .num_auto_selectable_formats = ARRAY_SIZE(ssm3515_selectable_formats),
225 };
226
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-07 13:14 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=202604072139.9CeDasUz-lkp@intel.com \
--to=lkp@intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--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.