public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Brahmajit Das <listout@listout.xyz>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.de>,
	 linux-sound@vger.kernel.org, linux-next@vger.kernel.org,
	liam.r.girdwood@linux.intel.com,  peter.ujfalusi@linux.intel.com,
	tiwai@suse.com
Subject: Re: [PATCH] ASoC: Intel: avs: replace strcmp with sysfs_streq
Date: Tue, 30 Dec 2025 14:02:21 +0530	[thread overview]
Message-ID: <aVOKgHJ4NXs5mKe_@localhost> (raw)
In-Reply-To: <3cd18fd0-6fef-4804-9474-41a500329e6f@intel.com>

On 29.12.2025 11:03, Cezary Rojewski wrote:
> On 2025-12-24 12:35 PM, Mark Brown wrote:
> > On Wed, Dec 24, 2025 at 11:05:56AM +0100, Takashi Iwai wrote:
> > 
> > > I believe it's a false positive, too.
> > > Or is it about potentially unterminated strings?
> > 
> > Regardless of the warning being spurious or not the cleanup seems like a
> > sensible one.
> 
...
> Brahmajit,
> 
> While I'm sure you did, just to be sure - did you try clean-rebuild with the
> 44-hardcode proposed by Amadeusz? We wouldn't want any old-artifacts to get
> in the way.
> 
> 
> Kind regards,
> Czarek

Czarek,

Not sure if it would help but I tracked or narrowed down the issue to
this section of the code in the avs_condpaths_walk function.


	if (avs_tplg_path_template_id_equal(&template->source,
										&template->sink) && dir)
		continue;

If I just comment that code segment out, then it builds successfully;
both with and without the hard coded name length.

I was also looking into GCC bugzilla and there seems to lot of reports
saying these kind of error could be bogus or false positive. I'm not
familiar with GCC internal or experienced in compilers to say/understand
whether this case in particular is a false positive or not.

BTW I can't seem to send the email to Amadeusz, hence removing them from
the CC-list
> msmtp: recipient address amade@asmblr.net not accepted by the server
-- 
Regards,
listout

  parent reply	other threads:[~2025-12-30  8:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-21 18:55 [PATCH] ASoC: Intel: avs: replace strcmp with sysfs_streq Brahmajit Das
2025-12-23 17:07 ` Mark Brown
2025-12-23 18:24   ` Amadeusz Sławiński
2025-12-23 20:57     ` Brahmajit Das
2025-12-24 10:05       ` Takashi Iwai
2025-12-24 11:35         ` Mark Brown
2025-12-29 10:03           ` Cezary Rojewski
2025-12-30  7:59             ` Brahmajit Das
2025-12-30  8:32             ` Brahmajit Das [this message]
2025-12-30  9:36               ` Cezary Rojewski
2025-12-30 12:25                 ` Amadeusz Sławiński
2025-12-30 14:47                   ` Richard Biener

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=aVOKgHJ4NXs5mKe_@localhost \
    --to=listout@listout.xyz \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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