From: Mark Brown <broonie@kernel.org>
To: Cheng-Yi Chiang <cychiang@chromium.org>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
alsa-devel@alsa-project.org, dgreid@chromium.org,
tzungbi@chromium.org, Rohit kumar <rohitkr@codeaurora.org>
Subject: Re: [PATCH v3 1/3] mfd: cros_ec: Add commands to control codec
Date: Mon, 7 Jan 2019 19:24:02 +0000 [thread overview]
Message-ID: <20190107192402.GW9570@sirena.org.uk> (raw)
In-Reply-To: <20181226070317.72022-1-cychiang@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
On Wed, Dec 26, 2018 at 03:03:15PM +0800, Cheng-Yi Chiang wrote:
> Note: This patch is merged to mfd tree for-mfd-next branch already.
> But this is still needed on sound tree for-next branch in order to
> compile cros_ec_codec driver.
Is there a tag I can merge?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-07 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 7:03 [PATCH v3 1/3] mfd: cros_ec: Add commands to control codec Cheng-Yi Chiang
2018-12-26 7:03 ` [PATCH v3 2/3] ASoC: Documentation: Add google,cros-ec-codec Cheng-Yi Chiang
2018-12-26 7:03 ` [PATCH v3 3/3] ASoC: cros_ec_codec: Add codec driver for Cros EC Cheng-Yi Chiang
2019-01-16 6:18 ` [alsa-devel] " Guenter Roeck
2019-01-16 22:59 ` Guenter Roeck
2019-01-17 4:25 ` Cheng-yi Chiang
2019-01-17 4:34 ` Guenter Roeck
2019-01-18 9:05 ` Cheng-yi Chiang
2019-01-07 19:24 ` Mark Brown [this message]
2019-01-08 9:54 ` [PATCH v3 1/3] mfd: cros_ec: Add commands to control codec Lee Jones
2019-01-08 16:12 ` Mark Brown
[not found] ` <CAFv8NwK4=m1ffsyTruMPw534FVK6QBeaMKxxW461aS_yNYugNg@mail.gmail.com>
2019-01-28 6:50 ` Lee Jones
2019-01-29 6:54 ` Cheng-yi Chiang
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=20190107192402.GW9570@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bleung@chromium.org \
--cc=cychiang@chromium.org \
--cc=dgreid@chromium.org \
--cc=groeck@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rohitkr@codeaurora.org \
--cc=tzungbi@chromium.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;
as well as URLs for NNTP newsgroup(s).