From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Scott Ling <sl@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: wm0010: Split out the firmware file parsing from the boot.
Date: Wed, 7 Nov 2012 15:32:55 +0100 [thread overview]
Message-ID: <20121107143253.GE20844@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1352292269-15021-1-git-send-email-sl@opensource.wolfsonmicro.com>
[-- Attachment #1.1: Type: text/plain, Size: 311 bytes --]
On Wed, Nov 07, 2012 at 12:44:29PM +0000, Scott Ling wrote:
> Move the firmware load and record parsing functionality out into
> a separate function from the boot function.
This still doesn't apply. What are you generating these against? Code
for upstream should be generated against the current upstream...
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
parent reply other threads:[~2012-11-07 14:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1352292269-15021-1-git-send-email-sl@opensource.wolfsonmicro.com>]
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=20121107143253.GE20844@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sl@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