linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/2] ASoC drivers for the Freescale MPC8610 SoC
Date: Tue, 08 Jan 2008 12:38:12 +0000	[thread overview]
Message-ID: <1199795892.19903.74.camel@localhost.localdomain> (raw)
In-Reply-To: <1199732204949-git-send-email-timur@freescale.com>

On Mon, 2008-01-07 at 12:56 -0600, Timur Tabi wrote:
> These patches add ALSA SoC device drivers for the Freescale MPC8610 SoC
> and the MPC8610-HPCD reference board.
> 
> The first patch updates some files in arch/powerpc and booting-without-of.txt.
> 
> The second patch adds the new audio driver files to sound/soc.
> 
> Both must be applied in order to avoid a build break.
> 
 
Both applied to the dev branch. This should let others use them atm and
allow us to port to ASoC v2.

I'll make a start on the port now.

Liam

  parent reply	other threads:[~2008-01-08 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 18:56 [PATCH 0/2] ASoC drivers for the Freescale MPC8610 SoC Timur Tabi
2008-01-07 18:56 ` [PATCH v2] [POWERPC] Update MPC8610 HPCD to support audio drivers Timur Tabi
2008-01-07 18:56   ` [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC Timur Tabi
2008-01-08 16:20     ` Liam Girdwood
2008-01-08  0:56   ` [PATCH v2] [POWERPC] Update MPC8610 HPCD to support audio drivers Stephen Rothwell
2008-01-08 12:39     ` Liam Girdwood
2008-01-10 16:35   ` Grant Likely
2008-01-08 12:38 ` Liam Girdwood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-10 22:44 [PATCH 0/2] ASoC drivers for the Freescale MPC8610 SoC Timur Tabi
2007-12-20 19:56 Timur Tabi

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=1199795892.19903.74.camel@localhost.localdomain \
    --to=lg@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.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).