From: kernel test robot <lkp@intel.com>
To: George Lander <lander@jagmn.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Marcus Cooper <codekipper@gmail.com>
Subject: sound/soc/sunxi/sun4i-spdif.c:180: warning: Function parameter or struct member 'mclk_multiplier' not described in 'sun4i_spdif_quirks'
Date: Fri, 31 Jan 2025 19:28:43 +0800 [thread overview]
Message-ID: <202501311953.0Ox9CW5w-lkp@intel.com> (raw)
Hi George,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 69e858e0b8b2ea07759e995aa383e8780d9d140c
commit: 0a2319308de88b9e819c0b43d0fccd857123eb31 ASoC: sun4i-spdif: Add clock multiplier settings
date: 8 weeks ago
config: mips-randconfig-r024-20220830 (https://download.01.org/0day-ci/archive/20250131/202501311953.0Ox9CW5w-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 12.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250131/202501311953.0Ox9CW5w-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/202501311953.0Ox9CW5w-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/sunxi/sun4i-spdif.c:180: warning: Function parameter or struct member 'mclk_multiplier' not described in 'sun4i_spdif_quirks'
vim +180 sound/soc/sunxi/sun4i-spdif.c
f8260afa444b67 Marcus Cooper 2016-02-08 167
ae9cccc30f6c08 Clément Péron 2019-05-27 168 /**
ae9cccc30f6c08 Clément Péron 2019-05-27 169 * struct sun4i_spdif_quirks - Differences between SoC variants.
ae9cccc30f6c08 Clément Péron 2019-05-27 170 *
c7202a19cf838d Lee Jones 2020-07-09 171 * @reg_dac_txdata: TX FIFO offset for DMA config.
ae9cccc30f6c08 Clément Péron 2019-05-27 172 * @has_reset: SoC needs reset deasserted.
f6a86b436b2658 Clément Péron 2019-05-27 173 * @val_fctl_ftx: TX FIFO flush bitmask.
ae9cccc30f6c08 Clément Péron 2019-05-27 174 */
ae9cccc30f6c08 Clément Péron 2019-05-27 175 struct sun4i_spdif_quirks {
ae9cccc30f6c08 Clément Péron 2019-05-27 176 unsigned int reg_dac_txdata;
ae9cccc30f6c08 Clément Péron 2019-05-27 177 bool has_reset;
f6a86b436b2658 Clément Péron 2019-05-27 178 unsigned int val_fctl_ftx;
0a2319308de88b George Lander 2024-11-11 179 unsigned int mclk_multiplier;
ae9cccc30f6c08 Clément Péron 2019-05-27 @180 };
ae9cccc30f6c08 Clément Péron 2019-05-27 181
:::::: The code at line 180 was first introduced by commit
:::::: ae9cccc30f6c088dd6ead63e990407e37cd9437b ASoC: sun4i-spdif: Move quirks to the top
:::::: TO: Clément Péron <peron.clem@gmail.com>
:::::: CC: Mark Brown <broonie@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-01-31 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 11:28 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-06 1:09 sound/soc/sunxi/sun4i-spdif.c:180: warning: Function parameter or struct member 'mclk_multiplier' not described in 'sun4i_spdif_quirks' kernel test robot
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=202501311953.0Ox9CW5w-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=codekipper@gmail.com \
--cc=lander@jagmn.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox