From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Shuah Khan <shuah@kernel.org>,
alsa-devel@alsa-project.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] kselftest/alsa - mixer-test: Log values associated with event issues
Date: Fri, 24 Mar 2023 07:50:29 +0100 [thread overview]
Message-ID: <87bkkihccq.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230322-alsa-mixer-event-values-v1-1-78189fcf6655@kernel.org>
On Wed, 22 Mar 2023 16:18:07 +0100,
Mark Brown wrote:
>
> While it is common for driver bugs with events to apply to all events there
> are some issues which only trigger for specific values. Understanding these
> is easier if we know what we were trying to do when configuring the control
> so add logging for the specific values involved in the spurious event.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Thanks, applied now.
Takashi
prev parent reply other threads:[~2023-03-24 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 15:18 [PATCH] kselftest/alsa - mixer-test: Log values associated with event issues Mark Brown
2023-03-24 6:50 ` 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=87bkkihccq.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kselftest@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