public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel•com>
To: Brahmajit Das <listout@listout•xyz>
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 10:36:27 +0100	[thread overview]
Message-ID: <4b85c90a-727e-43a2-b1bc-91dd00045e90@intel.com> (raw)
In-Reply-To: <aVOKgHJ4NXs5mKe_@localhost>

On 2025-12-30 9:32 AM, Brahmajit Das wrote:
> On 29.12.2025 11:03, Cezary Rojewski wrote:

...

>> 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.

Outstanding! Thank you for this exercise.

> 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.

Wouldn't be the first time, though having successful builds ain't wrong 
either. After all we have git log and incremental changes/reverts are 
not a problem.

> 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

That's weird. The @linux.intel.com is gone but what you mentioned is the 
correct one.

  reply	other threads:[~2025-12-30  9:36 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
2025-12-30  9:36               ` Cezary Rojewski [this message]
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=4b85c90a-727e-43a2-b1bc-91dd00045e90@intel.com \
    --to=cezary.rojewski@intel$(echo .)com \
    --cc=broonie@kernel$(echo .)org \
    --cc=liam.r.girdwood@linux$(echo .)intel.com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-sound@vger$(echo .)kernel.org \
    --cc=listout@listout$(echo .)xyz \
    --cc=peter.ujfalusi@linux$(echo .)intel.com \
    --cc=tiwai@suse$(echo .)com \
    --cc=tiwai@suse$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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