From: Kevin Hilman <khilman@deeprootsystems.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Olaya, Margarita" <magi.olaya@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCHv6 2/2][RESEND] ASoC: TWL6040: Add twl6040 codec driver
Date: Thu, 18 Mar 2010 11:28:21 -0700 [thread overview]
Message-ID: <87d3z1jxh6.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100318181623.GG6142@rakim.wolfsonmicro.main> (Mark Brown's message of "Thu\, 18 Mar 2010 18\:16\:23 +0000")
Mark Brown <broonie@opensource.wolfsonmicro.com> writes:
> On Thu, Mar 18, 2010 at 12:59:49PM -0500, Olaya, Margarita wrote:
>> From: Misael Lopez Cruz <x0052729@ti.com>
>>
>> Initial version of TWL6040 codec driver.
>>
>> The TWL6040 codec uses a proprietary PDM-based digital audio interface.
>> Audio paths supported are:
>
> I'm getting exactly the same results trying to apply this. It looks
> like there's some MUA corruption going on here,
In addition, checkpatch reports a pile of whitespace problems,
suggesting that all the tabs have been converted by spaces as well,
another sign of Outlook mis-behavior.
[...]
> Looks like MUA trouble. From the message headers it looks like you
> might be using Outlook or something, I'm not sure what to suggest for
> that - enough folks at TI are submitting patches that something must've
> been worked out for your mail system.
Indeed, You need to get outlook out of the picture for sending patches.
Using git-format-patch + git-send-email directly to your SMTP servers
seems to be working well for others inside TI.
Kevin
next prev parent reply other threads:[~2010-03-18 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 17:59 [PATCHv6 2/2][RESEND] ASoC: TWL6040: Add twl6040 codec driver Olaya, Margarita
2010-03-18 18:16 ` Mark Brown
2010-03-18 18:28 ` Kevin Hilman [this message]
2010-03-18 20:37 ` Olaya, Margarita
2010-03-18 18:38 ` Olaya, Margarita
2010-03-19 11:27 ` 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=87d3z1jxh6.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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