public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [morimoto:sound-cleanup-2026-04-06 119/119] Warning: sound/soc/soc-component.c:471 expecting prototype for snd_soc_component_regmap_cache_sync(). Prototype was for snd_soc_component_regmap_regcache_sync() instead
Date: Tue, 07 Apr 2026 12:03:14 +0800	[thread overview]
Message-ID: <202604071039.eCEs16hJ-lkp@intel.com> (raw)

tree:   https://github.com/morimoto/linux sound-cleanup-2026-04-06
head:   557e71769b656376e9a03618f6e770bb6a3defd5
commit: 89bf1d2520ff02f48039d27411baf6b923f0b16d [119/119] ASoC: soc-component: rename snd_soc_component_regmap_cache_sync()
config: powerpc-randconfig-001-20260406 (https://download.01.org/0day-ci/archive/20260407/202604071039.eCEs16hJ-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260407/202604071039.eCEs16hJ-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/202604071039.eCEs16hJ-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: sound/soc/soc-component.c:471 expecting prototype for snd_soc_component_regmap_cache_sync(). Prototype was for snd_soc_component_regmap_regcache_sync() instead

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

                 reply	other threads:[~2026-04-07  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=202604071039.eCEs16hJ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=llvm@lists.linux.dev \
    --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