From: Takashi Iwai <tiwai@suse.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Mark Brown <broonie@kernel.org>,
linux-sound@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: testing/selftests/alsa/mixer-test: 10 failures on Dell XPS 13 9360
Date: Fri, 31 May 2024 17:17:43 +0200 [thread overview]
Message-ID: <87cyp280yw.wl-tiwai@suse.de> (raw)
In-Reply-To: <1d44be36-9bb9-4d82-8953-5ae2a4f09405@molgen.mpg.de>
On Fri, 31 May 2024 07:50:33 +0200,
Paul Menzel wrote:
>
> Dear Linux folks,
>
>
> Running the ALSA kselftests with Linux 6.10-rc1, `mixer-test` shows
> ten failures:
>
> # Totals: pass:24 fail:0 xfail:0 xpass:0 skip:11 error:0
>
> These are:
>
> not ok 5 write_invalid.0.40
> not ok 11 write_valid.0.39
> not ok 18 write_valid.0.38
> not ok 25 write_valid.0.37
> not ok 201 write_invalid.0.12
> not ok 208 write_invalid.0.11
> not ok 264 write_invalid.0.3
> not ok 271 write_invalid.0.2
> not ok 278 write_invalid.0.1
> not ok 285 write_invalid.0.0
Through a quick look, those are no real "failures". It'd be more
preferable if the driver returns an error for invalid values, but
currently it's up to drivers how to deal with them, and some accept as
is but with correction of the values internally. They are shown as
"skips" in the summary above you showed, after all.
A more strict check can be enabled by a kconfig option
CONFIG_SND_CTL_INPUT_VALIDATION=y generically.
thanks,
Takashi
next prev parent reply other threads:[~2024-05-31 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 5:50 testing/selftests/alsa/mixer-test: 10 failures on Dell XPS 13 9360 Paul Menzel
2024-05-31 15:17 ` Takashi Iwai [this message]
2024-05-31 15:25 ` Paul Menzel
2024-05-31 16:03 ` Mark Brown
2024-05-31 18:06 ` Takashi Iwai
2024-06-03 11:38 ` Mark Brown
2024-06-14 11:33 ` Takashi Iwai
2024-06-14 11:42 ` Jaroslav Kysela
2024-06-14 12:38 ` Takashi Iwai
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=87cyp280yw.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pmenzel@molgen.mpg.de \
--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