From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Prchal Jiří" <jiri.prchal@aksignal.cz>
Cc: slapin@ossfans.org, alsa-devel@alsa-project.org,
support@atmel.com, lrg@slimlogic.co.uk
Subject: Re: PROBLEM: Asoc driver in 2.6.37.3 for AT91SAM9260 / TLV320AIC3X is broken
Date: Wed, 23 Mar 2011 13:54:58 +0000 [thread overview]
Message-ID: <20110323135457.GC25754@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4D89FB52.60405@aksignal.cz>
On Wed, Mar 23, 2011 at 02:53:22PM +0100, Prchal Jiří wrote:
> I also add SPI functionality and external clock on BCLK to codec tlv320aic3x.
> I'm sending diff, is this the right way to add it as patch to kernel releases?
Please see Documentation/SubmittingPatches for the process for sending
patches.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2011-03-23 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 8:58 PROBLEM: Asoc driver in 2.6.37.3 for AT91SAM9260 / TLV320AIC3X is broken Prchal Jiří
2011-03-11 15:05 ` Jarkko Nikula
2011-03-14 6:35 ` Prchal Jiří
2011-03-23 13:53 ` Prchal Jiří
2011-03-23 13:54 ` 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=20110323135457.GC25754@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jiri.prchal@aksignal.cz \
--cc=lrg@slimlogic.co.uk \
--cc=slapin@ossfans.org \
--cc=support@atmel.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;
as well as URLs for NNTP newsgroup(s).