From: Kevin Hilman <khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
To: Mark Brown <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
Cc: alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org
Subject: Re: [alsa-devel] [PATCH] ARM DaVinci: Add Right-Justified mode and Codec clock master to davinci-i2s
Date: Thu, 13 Nov 2008 06:56:57 -0800 [thread overview]
Message-ID: <878wrnk72e.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20081110114223.GB12804-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> (Mark Brown's message of "Mon\, 10 Nov 2008 11\:42\:24 +0000")
Mark Brown <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> writes:
> On Sat, Nov 08, 2008 at 01:26:09PM -0500, hugo.villeneuve-alTlfEjb/c1BDgjK7y7TUQ@public.gmane.org wrote:
>> From: Hugo Villeneuve <hugo.villeneuve-alTlfEjb/c1BDgjK7y7TUQ@public.gmane.org>
>
>> ARM DaVinci: Add Right-Justified mode and Codec clock master to davinci-i2s
>
> Not a big deal but you shouldn't repeat the subject line of your patch
> in the body - it causes automated tools like git am to duplicate it in
> the commit mesage.
>
>> The TI DVEVM board uses the SND_SOC_DAIFMT_CBM_CFM & I2S formats, but the
>> Lyrtech SFFSDR board uses the SND_SOC_DAIFMT_CBM_CFS & RIGHT-JUSTIFIED formats.
>
> Is there any news on the progress of the new DaVinci DMA API to
> mainline?
>
>> Signed-off-by: Hugo Villeneuve <hugo.villeneuve-alTlfEjb/c1BDgjK7y7TUQ@public.gmane.org>
>
> Acked-by: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
>
OK, pulling into DaVinci git and will drop when resync with next ASoC.
Kevin
prev parent reply other threads:[~2008-11-13 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 18:26 [PATCH] ARM DaVinci: Add Right-Justified mode and Codec clock master to davinci-i2s hugo.villeneuve
2008-11-10 11:42 ` Mark Brown
2008-11-10 15:06 ` Hugo Villeneuve
[not found] ` <20081110114223.GB12804-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2008-11-13 14:56 ` Kevin Hilman [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=878wrnk72e.fsf@deeprootsystems.com \
--to=khilman-1d3hcaltpluheniveurvkkeocmrvltnr@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.