From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>, 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, 02 Dec 2022 08:54:44 +0100 [thread overview]
Message-ID: <87wn7akzp7.wl-tiwai@suse.de> (raw)
In-Reply-To: <87y1rqkzto.wl-tiwai@suse.de>
On Fri, 02 Dec 2022 08:52:03 +0100,
Takashi Iwai wrote:
>
> On Thu, 01 Dec 2022 21:29:48 +0100,
> Mark Brown wrote:
> >
> > On Thu, Dec 01, 2022 at 08:06:22PM +0100, Takashi Iwai wrote:
> > > On Thu, 01 Dec 2022 18:42:22 +0100,
> > > Jaroslav Kysela wrote:
> > > >
> > > > Let me know, if I can stack your changes on top, or perhaps, you may
> > > > be willing to adapt them.
> > >
> > > As Mark has already sent a v2 series, I applied his v2 at first.
> > > Could you rebase and resubmit on top of my for-next branch?
> >
> > 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.
Apologies for the mess.
Takashi
next prev parent reply other threads:[~2022-12-02 7:56 UTC|newest]
Thread overview: 17+ 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 ` [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 ` [PATCH v1 2/6] kselftest/alsa: Report failures to set the requested sample rate as skips 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 ` [PATCH v1 4/6] kselftest/alsa: Don't any configuration in the sample config 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 ` [PATCH v1 6/6] kselftest/alsa: Add more coverage of sample rates and channel counts Mark Brown
2022-11-30 13:42 ` Mark Brown
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 19:06 ` Takashi Iwai
2022-12-01 20:29 ` Mark Brown
2022-12-02 7:52 ` Takashi Iwai
2022-12-02 7:54 ` Takashi Iwai [this message]
2022-12-02 8:56 ` Jaroslav Kysela
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=87wn7akzp7.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 \
/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