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: Mon, 10 Jul 2023 09:00:09 +0200 [thread overview]
Message-ID: <87wmz8i746.wl-tiwai@suse.de> (raw)
In-Reply-To: <06b8bfde-e4f1-48ea-aa3e-35d2fe5df046@sirena.org.uk>
On Wed, 21 Jun 2023 20:19:46 +0200,
Mark Brown wrote:
>
> On Wed, Jun 21, 2023 at 08:13:11PM +0200, Takashi Iwai wrote:
> > Mark Brown wrote:
>
> > > 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?
>
> For KernelCI we've got coverage on both. I can also run stuff on the
> boards I have in my lab on demand of course, but there's more coverage
> in KernelCI.
OK, now I applied those two patches to for-next branch (i.e. for 6.6
kernel). Let's watch out.
thanks,
Takashi
next prev parent reply other threads:[~2023-07-10 7:02 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
2023-06-21 18:19 ` Mark Brown
2023-07-10 7:00 ` Takashi Iwai [this message]
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=87wmz8i746.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.