From: Mark Brown <broonie@kernel.org>
To: Olivier MOYSAN <olivier.moysan@st.com>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"robh@kernel.org" <robh@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kernel@stlinux.com" <kernel@stlinux.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnaud POULIQUEN <arnaud.pouliquen@st.com>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>,
"rmk@arm.linux.org.uk" <rmk@arm.linux.org.uk>,
"jsarha@ti.com" <jsarha@ti.com>
Subject: Re: [PATCH 0/3] ASoC: stm32: sai: add support of iec958 controls
Date: Tue, 17 Apr 2018 12:17:33 +0100 [thread overview]
Message-ID: <20180417111733.GG8973@sirena.org.uk> (raw)
In-Reply-To: <a0552849-47fa-dc72-a512-a3e075adb07f@st.com>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On Tue, Apr 17, 2018 at 08:29:17AM +0000, Olivier MOYSAN wrote:
> I guess the blocking patch in this patchset is the patch "add IEC958
> channel status control helper". This patch has been reviewed several
> times, but did not get a ack so far.
> If you think these helpers will not be merged, I will reintegrate the
> corresponding code in stm driver.
> Please let me know, if I need to prepare a v2 without helpers, or if we
> can go further in the review of iec helpers patch ?
I don't mind either way but you're right here, I'm waiting for Takashi
to review the first patch. I'd probably be OK with it just integrated
into the driver if we have to go that way though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-17 11:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 16:27 [PATCH 0/3] ASoC: stm32: sai: add support of iec958 controls Olivier Moysan
2018-03-13 16:27 ` [PATCH 1/3] ALSA: pcm: add IEC958 channel status control helper Olivier Moysan
2018-03-13 16:27 ` [PATCH 2/3] ASoC: stm32: sai: add iec958 controls support Olivier Moysan
2018-06-05 15:52 ` Arnaud Pouliquen
2018-03-13 16:27 ` [PATCH 3/3] ASoC: dmaengine_pcm: document process callback Olivier Moysan
2018-03-13 16:47 ` Applied "ASoC: dmaengine_pcm: document process callback" to the asoc tree Mark Brown
2018-04-17 8:29 ` [PATCH 0/3] ASoC: stm32: sai: add support of iec958 controls Olivier MOYSAN
2018-04-17 11:17 ` Mark Brown [this message]
2018-05-17 13:03 ` Olivier MOYSAN
2018-06-05 15:50 ` [alsa-devel] " Arnaud Pouliquen
2018-06-05 18:29 ` Takashi Iwai
2018-06-06 9:31 ` Arnaud Pouliquen
2018-06-06 9:47 ` Takashi Iwai
2018-06-07 16:02 ` Arnaud Pouliquen
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=20180417111733.GG8973@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=kernel@stlinux.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@st.com \
--cc=perex@perex.cz \
--cc=rmk@arm.linux.org.uk \
--cc=robh@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 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).