From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Olaya, Margarita" <magi.olaya@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCHv6 2/2] ASoC: TWL6040: Add twl6040 codec driver
Date: Thu, 18 Mar 2010 17:17:38 +0000 [thread overview]
Message-ID: <20100318171737.GE6142@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1889FA7136B567478A67D4B0F85B0CCE662AC372@dlee06.ent.ti.com>
On Wed, Mar 17, 2010 at 05:42:38PM -0500, Olaya, Margarita wrote:
> From: Misael Lopez Cruz <x0052729@ti.com>
>
> Initial version of TWL6040 codec driver.
I'm having trouble applying this - using patch by hand says:
patching file sound/soc/codecs/Kconfig
Hunk #1 FAILED at 35.
Hunk #2 succeeded at 168 with fuzz 2.
1 out of 2 hunks FAILED -- saving rejects to file sound/soc/codecs/Kconfig.rej
patching file sound/soc/codecs/Makefile
Hunk #1 FAILED at 22.
patch: **** malformed patch at line 133: aic26.o
It looks like it should be some trivial rebasing things that need
sorting - I'd try to fix up by hand but the "malformed patch" warning is
making me worry something might be getting lost and I've no way of
testing the code. Could you please generate the patch against:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.35
just to be on the safe side. Only this patch ran into trouble, the
first one was fine.
prev parent reply other threads:[~2010-03-18 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 22:42 [PATCHv6 2/2] ASoC: TWL6040: Add twl6040 codec driver Olaya, Margarita
2010-03-18 8:43 ` Liam Girdwood
2010-03-18 17:17 ` 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=20100318171737.GE6142@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=magi.olaya@ti.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