From: Philip Li <philip.li@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: sound/soc/qcom/sdw.c:93: warning: cannot understand function prototype: 'ret = sdw_enable_stream(sruntime); '
Date: Wed, 30 Apr 2025 15:49:54 +0800 [thread overview]
Message-ID: <aBHWImb+uElWcLk2@rli9-mobl> (raw)
In-Reply-To: <CAMuHMdWWM=ftk3AYTQJFVcSUnYmqsYRLvK9un5OvR9poevBTgA@mail.gmail.com>
On Wed, Apr 30, 2025 at 08:43:55AM +0200, Geert Uytterhoeven wrote:
> On Tue, 29 Apr 2025 at 10:18, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > On 26/04/2025 15:32, kernel test robot wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > > head: 02ddfb981de88a2c15621115dd7be2431252c568
> > > commit: db7e59e6a39a4d3d54ca8197c796557e6d480b0d ASoC: qcom: sc7280: Fix missing Soundwire runtime stream alloc
> > > date: 6 months ago
> > > config: sh-randconfig-002-20250426 (https://download.01.org/0day-ci/archive/20250426/202504262154.sBmNTrcB-lkp@intel.com/config)
> > > compiler: sh4-linux-gcc (GCC) 12.4.0
> > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250426/202504262154.sBmNTrcB-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/202504262154.sBmNTrcB-lkp@intel.com/
> > >
> > > All warnings (new ones prefixed by >>):
> > >
> > >>> sound/soc/qcom/sdw.c:93: warning: cannot understand function prototype: 'ret = sdw_enable_stream(sruntime); '
> >
> > This looks like compiler issue. I check the config and SOUNDWIRE is
> > selected thus sdw_enable_stream() is reachable. I also cannot reproduce
> > it sh4-linux-gnu-gcc v14.2.
>
> I also couldn't reproduce it, using the specified commit ID and
> the reproducer instructions, with gcc versions 12.3.0 (Ubuntu
> 12.3.0-17ubuntu1) and 13.3.0 (Ubuntu 13.3.0-6ubuntu2~24.04).
Sorry for the false positive, it does appear during the bisection process and
results in this first bad commit, which could be related to kernel-doc.
But fail to reproduce it now as well on gcc-12.4. We will follow up to further
check the bisection process and reproduce steps.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
prev parent reply other threads:[~2025-04-30 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 13:32 sound/soc/qcom/sdw.c:93: warning: cannot understand function prototype: 'ret = sdw_enable_stream(sruntime); ' kernel test robot
2025-04-29 8:18 ` Krzysztof Kozlowski
2025-04-30 6:43 ` Geert Uytterhoeven
2025-04-30 7:49 ` Philip Li [this message]
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=aBHWImb+uElWcLk2@rli9-mobl \
--to=philip.li@intel.com \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox