From: Mark Brown <broonie@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: intel/skl/hda - export number of digital microphones via control components
Date: Thu, 28 Nov 2019 17:59:57 +0000 [thread overview]
Message-ID: <20191128175957.GG4210@sirena.org.uk> (raw)
In-Reply-To: <48159775-bd7b-b473-7e02-3116ca8dee73@perex.cz>
[-- Attachment #1.1: Type: text/plain, Size: 629 bytes --]
On Thu, Nov 28, 2019 at 03:28:19PM +0100, Jaroslav Kysela wrote:
> Dne 26. 11. 19 v 17:29 Mark Brown napsal(a):
> > You've missed the merge window already - it was open before this patch
> > was sent.
> So, what now? Rebase on top of Pierre patches? You added another patches to
> your for-5.5 branch today.
Since Pierre seems happy with it even if he didn't ack it explicitly
I'll guess I'll apply it. If git can figure out applying it after the
merge window and it doesn't get negative reviews there's no need to
resend. If it can't and it doesn't turn up in a bigger series before
then I'll let you know.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-28 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 10:34 [alsa-devel] [PATCH] ASoC: intel/skl/hda - export number of digital microphones via control components Jaroslav Kysela
2019-11-26 12:33 ` Pierre-Louis Bossart
2019-11-26 13:51 ` Jaroslav Kysela
2019-11-26 14:57 ` Pierre-Louis Bossart
2019-11-26 16:29 ` Mark Brown
2019-11-28 14:28 ` Jaroslav Kysela
2019-11-28 17:59 ` Mark Brown [this message]
2019-11-28 18:03 ` Jaroslav Kysela
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=20191128175957.GG4210@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).