From: Mark Brown <broonie@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>, Shuah Khan <shuah@kernel.org>,
alsa-devel@alsa-project.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v1 0/6] kselftest/alsa: pcm-test improvements
Date: Fri, 2 Dec 2022 13:22:41 +0000 [thread overview]
Message-ID: <Y4n8IZbLvX0Eg/V9@sirena.org.uk> (raw)
In-Reply-To: <66bef382-e38f-85d5-0e07-3cf672a89882@perex.cz>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On Fri, Dec 02, 2022 at 09:56:39AM +0100, Jaroslav Kysela wrote:
> On 02. 12. 22 8:54, Takashi Iwai wrote:
> > Takashi Iwai wrote:
> > > > Oh, this is getting a little confusing - I'd just picked Jaroslav's
> > > > patch into my tree and was in the middle redoing my ideas on top of his
> > > > code! I might have something more later this evening... I think we can
> > > > converge here, let me continue taking a look.
> > > Ah then it was my misunderstanding, and everything should be fine now
> > > ;) Thanks!
> > Erm, you meant sent as *v3*. I've seen now.
> > As the v2 patches were already merged, could you rather rebase and
> > resubmit? I'd like to avoid rebase the full series that are already
> > included in linux-next.
> It's rebased. The first patch from the set drops the previous Mark's changes.
Indeed, there was so many collisions with Jaroslav's patches
which it just seemed like the most straightforward way to do
things (plus I'd already written a good chunk of the new version
by the time you applied my v2). Probably only a small bit of the
skipping code would end up remaining anyway.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v1 0/6] kselftest/alsa: pcm-test improvements
Date: Fri, 2 Dec 2022 13:22:41 +0000 [thread overview]
Message-ID: <Y4n8IZbLvX0Eg/V9@sirena.org.uk> (raw)
In-Reply-To: <66bef382-e38f-85d5-0e07-3cf672a89882@perex.cz>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On Fri, Dec 02, 2022 at 09:56:39AM +0100, Jaroslav Kysela wrote:
> On 02. 12. 22 8:54, Takashi Iwai wrote:
> > Takashi Iwai wrote:
> > > > Oh, this is getting a little confusing - I'd just picked Jaroslav's
> > > > patch into my tree and was in the middle redoing my ideas on top of his
> > > > code! I might have something more later this evening... I think we can
> > > > converge here, let me continue taking a look.
> > > Ah then it was my misunderstanding, and everything should be fine now
> > > ;) Thanks!
> > Erm, you meant sent as *v3*. I've seen now.
> > As the v2 patches were already merged, could you rather rebase and
> > resubmit? I'd like to avoid rebase the full series that are already
> > included in linux-next.
> It's rebased. The first patch from the set drops the previous Mark's changes.
Indeed, there was so many collisions with Jaroslav's patches
which it just seemed like the most straightforward way to do
things (plus I'd already written a good chunk of the new version
by the time you applied my v2). Probably only a small bit of the
skipping code would end up remaining anyway.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-12-02 13:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 0:06 [PATCH v1 0/6] kselftest/alsa: pcm-test improvements Mark Brown
2022-11-30 0:06 ` Mark Brown
2022-11-30 0:06 ` [PATCH v1 1/6] kselftest/alsa: Refactor pcm-test to list the tests to run in a struct Mark Brown
2022-11-30 0:06 ` Mark Brown
2022-11-30 0:06 ` [PATCH v1 2/6] kselftest/alsa: Report failures to set the requested sample rate as skips Mark Brown
2022-11-30 0:06 ` Mark Brown
2022-11-30 0:06 ` [PATCH v1 3/6] kselftest/alsa: Report failures to set the requested channels " Mark Brown
2022-11-30 0:06 ` Mark Brown
2022-11-30 0:06 ` [PATCH v1 4/6] kselftest/alsa: Don't any configuration in the sample config Mark Brown
2022-11-30 0:06 ` Mark Brown
2022-11-30 0:06 ` [PATCH v1 5/6] kselftest/alsa: Provide more meaningful names for tests Mark Brown
2022-11-30 0:06 ` Mark Brown
2022-11-30 0:06 ` [PATCH v1 6/6] kselftest/alsa: Add more coverage of sample rates and channel counts Mark Brown
2022-11-30 0:06 ` Mark Brown
2022-11-30 13:42 ` Mark Brown
2022-11-30 13:52 ` Takashi Iwai
2022-11-30 13:52 ` Takashi Iwai
2022-12-01 17:42 ` [PATCH v1 0/6] kselftest/alsa: pcm-test improvements Jaroslav Kysela
2022-12-01 18:44 ` Mark Brown
2022-12-01 18:44 ` Mark Brown
2022-12-01 19:06 ` Takashi Iwai
2022-12-01 19:06 ` Takashi Iwai
2022-12-01 20:29 ` Mark Brown
2022-12-01 20:29 ` Mark Brown
2022-12-02 7:52 ` Takashi Iwai
2022-12-02 7:52 ` Takashi Iwai
2022-12-02 7:54 ` Takashi Iwai
2022-12-02 7:54 ` Takashi Iwai
2022-12-02 8:56 ` Jaroslav Kysela
2022-12-02 8:56 ` Jaroslav Kysela
2022-12-02 13:22 ` Mark Brown [this message]
2022-12-02 13:22 ` 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=Y4n8IZbLvX0Eg/V9@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=perex@perex.cz \
--cc=shuah@kernel.org \
--cc=tiwai@suse.de \
/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.