From: kernel test robot <lkp@intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [freescale-fslc:6.1-2.1.x-imx 126/15770] sound/soc/fsl/fsl_easrc_m2m.c:19:6: sparse: sparse: symbol 'fsl_easrc_get_status' was not declared. Should it be static?
Date: Fri, 10 Nov 2023 01:09:32 +0800 [thread overview]
Message-ID: <202311100043.3vRGLPQk-lkp@intel.com> (raw)
tree: https://github.com/Freescale/linux-fslc 6.1-2.1.x-imx
head: 742924a05c8a6349d6d1fe67010a3c5ed54df884
commit: 46ac86d263c28d721f9f740b0e31d488ee95bc43 [126/15770] MLK-21940-4: ASoC: fsl_easrc: Support the m2m function
config: i386-randconfig-063-20231024 (https://download.01.org/0day-ci/archive/20231110/202311100043.3vRGLPQk-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231110/202311100043.3vRGLPQk-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/202311100043.3vRGLPQk-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
sound/soc/fsl/fsl_easrc.c: note: in included file:
>> sound/soc/fsl/fsl_easrc_m2m.c:19:6: sparse: sparse: symbol 'fsl_easrc_get_status' was not declared. Should it be static?
>> sound/soc/fsl/fsl_easrc_m2m.c:282:5: sparse: sparse: symbol 'fsl_easrc_process_buffer_pre' was not declared. Should it be static?
>> sound/soc/fsl/fsl_easrc_m2m.c:415:6: sparse: sparse: symbol 'fsl_easrc_submit_dma' was not declared. Should it be static?
vim +/fsl_easrc_get_status +19 sound/soc/fsl/fsl_easrc_m2m.c
18
> 19 void fsl_easrc_get_status(struct fsl_asrc_pair *ctx,
20 struct asrc_status_flags *flags)
21 {
22 flags->overload_error = 0;
23 }
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-09 17:13 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=202311100043.3vRGLPQk-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=otavio@ossystems.com.br \
/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.