From: Mark Brown <broonie@kernel.org>
To: Cheng-yi Chiang <cychiang@chromium.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org, Dylan Reid <dgreid@chromium.org>,
tzungbi@chromium.org, Rohit kumar <rohitkr@codeaurora.org>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH v4 2/2] ASoC: cros_ec_codec: Add codec driver for Cros EC
Date: Mon, 21 Jan 2019 17:54:01 +0000 [thread overview]
Message-ID: <20190121175401.GE12679@sirena.org.uk> (raw)
In-Reply-To: <CAFv8NwKctsH5cKUQxgfQNg3V2Y=-o5LFZC0b+jwLC=_nNumbig@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
On Sat, Jan 19, 2019 at 07:39:19PM +0800, Cheng-yi Chiang wrote:
> Hi Mark,
>
> Sorry, I forgot to mention that the patch for EC command definition
> has been already merged in upstream, but not in Mark's for-next tree
> yet.
>
> c1f3375be60c mfd: cros_ec: Add commands to control codec
>
> This is needed.
Right, I can't really apply these without that in my tree. Lee did say
he might send a signed tag for it but I don't think he did that yet. :(
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-21 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 11:33 [PATCH v4 1/2] ASoC: Documentation: Add google,cros-ec-codec Cheng-Yi Chiang
2019-01-19 11:33 ` [PATCH v4 2/2] ASoC: cros_ec_codec: Add codec driver for Cros EC Cheng-Yi Chiang
2019-01-19 11:39 ` Cheng-yi Chiang
2019-01-21 17:54 ` Mark Brown [this message]
2019-01-21 18:27 ` [alsa-devel] " Enric Balletbo Serra
2019-01-29 12:14 ` Applied "ASoC: cros_ec_codec: Add codec driver for Cros EC" to the asoc tree Mark Brown
2019-01-21 18:14 ` [alsa-devel] [PATCH v4 1/2] ASoC: Documentation: Add google, cros-ec-codec Enric Balletbo Serra
2019-01-29 12:14 ` Applied "ASoC: Documentation: Add google, cros-ec-codec" to the asoc tree 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=20190121175401.GE12679@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cychiang@chromium.org \
--cc=dgreid@chromium.org \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®