From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: "\"Nícolas F. R. A.\" Prado" <nfraprado@collabora.com>,
"Jaroslav Kysela" <perex@perex.cz>,
kernel@collabora.com,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Shuah Khan" <shuah@kernel.org>, "Takashi Iwai" <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 2/2] kselftest/alsa: pcm-test: Decrease stream duration from 4 to 2 seconds
Date: Wed, 21 Jun 2023 20:13:11 +0200 [thread overview]
Message-ID: <87wmzwptu0.wl-tiwai@suse.de> (raw)
In-Reply-To: <f5cab2c2-1638-4d19-aff3-d46ed34b857e@sirena.org.uk>
On Wed, 21 Jun 2023 19:08:27 +0200,
Mark Brown wrote:
>
> On Wed, Jun 21, 2023 at 06:34:22PM +0200, Takashi Iwai wrote:
>
> > So, we're back to square... Unless anyone has a strong objection, I'm
> > inclined to take this as a workaround for 6.5 for now, as the merge
> > window deadline is coming. We can improve things at the same time for
> > the future kernel, too.
>
> It feels like it might be good to let it cook for a bit longer before
> going to Linus (eg, applying after the merge window) so we've more
> chance to see what the impact is on other boards?
I'm fine with that option, too. Are most of selftests performed on
linux-next basis, or rather on Linus tree?
Takashi
next prev parent reply other threads:[~2023-06-21 18:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 22:08 [PATCH 0/2] kselftest/alsa: Decrease pcm-test duration to avoid timeouts Nícolas F. R. A. Prado
2023-06-20 22:08 ` [PATCH 1/2] kselftest/alsa: pcm-test: Move stream duration and margin to variables Nícolas F. R. A. Prado
2023-06-21 9:52 ` AngeloGioacchino Del Regno
2023-06-20 22:08 ` [PATCH 2/2] kselftest/alsa: pcm-test: Decrease stream duration from 4 to 2 seconds Nícolas F. R. A. Prado
2023-06-21 13:08 ` Mark Brown
2023-06-21 14:08 ` Jaroslav Kysela
2023-06-21 14:39 ` Mark Brown
2023-06-21 16:03 ` Nícolas F. R. A. Prado
2023-06-21 16:34 ` Takashi Iwai
2023-06-21 17:08 ` Mark Brown
2023-06-21 18:13 ` Takashi Iwai [this message]
2023-06-21 18:19 ` Mark Brown
2023-07-10 7:00 ` Takashi Iwai
2023-07-12 22:03 ` Mark Brown
2023-07-13 8:47 ` Takashi Iwai
2023-07-13 20:39 ` 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=87wmzwptu0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=nfraprado@collabora.com \
--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