From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] ASoC: wm_adsp: Add codec_probe and codec_remove stubs
Date: Thu, 11 Jun 2015 11:40:07 +0100 [thread overview]
Message-ID: <20150611104007.GR14071@sirena.org.uk> (raw)
In-Reply-To: <1434018752-523-1-git-send-email-rf@opensource.wolfsonmicro.com>
[-- Attachment #1.1: Type: text/plain, Size: 585 bytes --]
On Thu, Jun 11, 2015 at 11:32:30AM +0100, Richard Fitzgerald wrote:
> Currently the only init function in wm_adsp is called by the
> codec driver early in its probe before the codec has been
> registered with SOC.
I've applied these but for some reason it seems you've generated these
ADSP patches against topic/arizona. In general I'm going to expect
things to apply against the most obvious topic branch or at a push -next
(and to merge cleanly into -next), if you've got non-obvious
dependencies or dependencies on multiple branches then say so in your
cover letter.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-06-11 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 10:32 [PATCH v4 1/3] ASoC: wm_adsp: Add codec_probe and codec_remove stubs Richard Fitzgerald
2015-06-11 10:32 ` [PATCH v4 2/3] ASoC: wm_adsp: create ALSA controls from wm_adsp driver Richard Fitzgerald
2015-06-11 10:32 ` [PATCH v4 3/3] ASoC: wm_adsp: Add basic debugfs entries Richard Fitzgerald
2015-06-11 10:40 ` Mark Brown [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=20150611104007.GR14071@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=rf@opensource.wolfsonmicro.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