public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>, Shuah Khan <shuah@kernel.org>,
	linux-sound@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kselftest/alsa: Use card name rather than number in test names
Date: Mon, 15 Jul 2024 15:23:24 +0200	[thread overview]
Message-ID: <87le2223hv.wl-tiwai@suse.de> (raw)
In-Reply-To: <652d6fef-9e63-4c3c-b61b-8a47d6eadaf1@sirena.org.uk>

On Mon, 15 Jul 2024 15:18:44 +0200,
Mark Brown wrote:
> 
> On Sat, Jul 13, 2024 at 08:46:43AM +0200, Takashi Iwai wrote:
> > Mark Brown wrote:
> 
> > OTOH, if the former is the problem, using longname won't help,
> > either, rather it can be confusing.  I noticed that the test output
> > truncates the name string, hence both cards look identical in the
> > actual output (except for the card listing at the beginning).
> 
> Interesting - I was mainly developing on a system with multiple HDA
> cards and was getting fairly clearly unique names.

An AMD system usually has two HD-audio entries, and both are "HD-audio
Generic".


Takashi

  reply	other threads:[~2024-07-15 13:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 14:33 [PATCH] kselftest/alsa: Use card name rather than number in test names Mark Brown
2024-07-11 16:08 ` Jaroslav Kysela
2024-07-11 16:19   ` Mark Brown
2024-07-12  8:21     ` Takashi Iwai
2024-07-12  9:20       ` Jaroslav Kysela
2024-07-12 13:00         ` Mark Brown
2024-07-12 16:25           ` Jaroslav Kysela
2024-07-12 18:19             ` Mark Brown
2024-07-13  6:46               ` Takashi Iwai
2024-07-15 13:18                 ` Mark Brown
2024-07-15 13:23                   ` Takashi Iwai [this message]
2024-07-15 17:31                     ` Mark Brown
2024-07-13  7:35               ` Jaroslav Kysela
2024-07-15 12:48                 ` Mark Brown

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=87le2223hv.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=shuah@kernel.org \
    --cc=tiwai@suse.com \
    /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