Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Ian Bridges <icb@fastmail.org>
Cc: Takashi Iwai <tiwai@suse.de>, linux-sound@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: Add hda_append_suffix() local helper
Date: Fri, 31 Jul 2026 08:40:32 +0200	[thread overview]
Message-ID: <87bjbn1x27.wl-tiwai@suse.de> (raw)
In-Reply-To: <amuQK0k9uIalPCxA@dev>

On Thu, 30 Jul 2026 19:55:55 +0200,
Ian Bridges wrote:
> 
> On Thu, Jul 30, 2026 at 06:14:03PM +0200, Takashi Iwai wrote:
> > As strlcat() shall be deprecated in future, provide an alternative
> > just for a simple purpose -- append a suffix string to the given
> > string buffer -- and use it at appropriate places.  The code isn't
> > really efficient, but we don't ask for speed here, so let it be.
> 
> The patch was tested as follows:
>  - Applied on today's for-next (f817bac425c5) on top of the two jack
>  name cleanup patches. W=1 build of sound/hda/, no new warnings.
> 
>  - A userspace harness compared hda_append_suffix() against
>  both the kernel strlcat() and the strncat() form in jack.c,
>  exhaustively over buffer sizes, fill levels and suffix
>  lengths, comparing every byte of the buffer. All cases
>  were byte identical, including truncation.
> 
>  - A QEMU boot with intel-hda and hda-duplex, comparing the PCM
>  stream names, the codec proc dump and the full control
>  element list between base and patched kernels. The captures
>  were byte identical.
> 
> Ian
> 
> Reviewed-by: Ian Bridges <icb@fastmail.org>
> Tested-by: Ian Bridges <icb@fastmail.org>

Thanks for checking.  Applied now to for-next branch.


Takashi

      reply	other threads:[~2026-07-31  6:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 16:14 [PATCH] ALSA: hda: Add hda_append_suffix() local helper Takashi Iwai
2026-07-30 17:55 ` Ian Bridges
2026-07-31  6:40   ` Takashi Iwai [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=87bjbn1x27.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=icb@fastmail.org \
    --cc=linux-sound@vger.kernel.org \
    /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