From: "Gorski, Mateusz" <mateusz.gorski@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: cezary.rojewski@intel.com, alsa-devel@alsa-project.org,
tiwai@suse.com, pierre-louis.bossart@linux.intel.com
Subject: Re: [PATCH v4 0/3] Add support for different DMIC configurations
Date: Mon, 27 Apr 2020 13:14:47 +0200 [thread overview]
Message-ID: <24bdfe47-104b-e87a-db97-ce0dccdb0662@linux.intel.com> (raw)
In-Reply-To: <20200424145236.GG5850@sirena.org.uk>
>> Set of patches to enable DMIC capture on different hardware
>> configurations.
> Neither this posting nor the last posting seem to have managed to send
> me a copy of patch 2.
The only reason I can think of is the fact, that one of Signed-by tags
in patch 2/3 had a comma in it and git send-patch added one additional,
invalid CC recipient.
I have adjusted that Signed-by tag in patchset v5.
Mateusz
prev parent reply other threads:[~2020-04-27 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 13:19 [PATCH v4 0/3] Add support for different DMIC configurations Mateusz Gorski
2020-04-24 13:20 ` [PATCH v4 1/3] ASoC: Intel: Skylake: Add alternative topology binary name Mateusz Gorski
2020-04-24 13:20 ` [PATCH v4 2/3] ASoC: Intel: Multiple I/O PCM format support for pipe Mateusz Gorski
2020-04-24 15:26 ` Pierre-Louis Bossart
2020-04-27 11:14 ` Gorski, Mateusz
2020-04-24 13:20 ` [PATCH v4 3/3] ASoC: Intel: Skylake: Automatic DMIC format configuration according to information from NHLT Mateusz Gorski
2020-04-24 14:52 ` [PATCH v4 0/3] Add support for different DMIC configurations Mark Brown
2020-04-27 11:14 ` Gorski, Mateusz [this message]
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=24bdfe47-104b-e87a-db97-ce0dccdb0662@linux.intel.com \
--to=mateusz.gorski@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).