Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 10/14] ASoC: multi-component - Analog Devices Blackfin Platform
Date: Thu, 12 Aug 2010 08:57:17 +0100	[thread overview]
Message-ID: <1281599837.3067.7.camel@odin> (raw)
In-Reply-To: <AANLkTi=iQiRkx1iJFMNJ5WeMONBVyRVVY3sYDxK67Tcx@mail.gmail.com>

On Wed, 2010-08-11 at 23:47 -0400, Mike Frysinger wrote:
> On Wed, Aug 11, 2010 at 23:46, Mike Frysinger wrote:
> > for Blackfin changes, please use our mailing list:
> > uclinux-dist-devel@blackfin.uclinux.org
> 
> actually, this should be for all ADI changes (including Blackfin
> processors).  i guess i should add MAINTAINERS entries for this.

That would be good if your willing to help out and maintain the ASoC AD
codecs and Blackfin support. I did initially email Sedji, but it looks
like he no longer works for Analog Devices.  

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

  reply	other threads:[~2010-08-12  7:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11  8:46 [PATCH 00/14] ASoC: multi-component platform support Liam Girdwood
2010-08-11  8:46 ` [PATCH 01/14] ASoC: multi-component - TI OMAP Platform Liam Girdwood
2010-08-11 11:04   ` Jarkko Nikula
2010-08-11 11:44     ` Liam Girdwood
2010-08-11  8:46 ` [PATCH 02/14] ASoC: multi-component - Atmel Platform Liam Girdwood
2010-08-18  9:28   ` Nicolas Ferre
2010-08-11  8:46 ` [PATCH 03/14] ASoC: multi-component - TI DaVinci Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 04/14] ASoC: multi-component - Freescale i.MX Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 05/14] ASoC: multi-component - Toshiba Txx9 Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 06/14] ASoC: multi-component - Renasas SuperH Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 07/14] ASoC: multi-component - S6000 Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 08/14] ASoC: multi-component - Freescale PPC Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 09/14] ASoC: multi-component - RMI Alchemy AU1x Platform Liam Girdwood
2010-08-11 18:34   ` Manuel Lauss
2010-08-11 21:07     ` Liam Girdwood
2010-08-12 13:15       ` Liam Girdwood
2010-08-11  8:46 ` [PATCH 10/14] ASoC: multi-component - Analog Devices Blackfin Platform Liam Girdwood
2010-08-12  3:46   ` Mike Frysinger
2010-08-12  3:47     ` Mike Frysinger
2010-08-12  7:57       ` Liam Girdwood [this message]
2010-08-12 11:17         ` Mike Frysinger
2010-08-12 11:30           ` Liam Girdwood
2010-08-12 11:33             ` Liam Girdwood
2010-08-12 11:56               ` Mike Frysinger
2010-08-12 10:34       ` Mark Brown
2010-08-11  8:46 ` [PATCH 11/14] ASoC: multi-component - Cirrus Logic ep93xx Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 12/14] ASoC: multi-component - Marvell Kirkwood Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 13/14] ASoC: multi-component - Winbond/Nuvoton NUC900 Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 14/14] ASoC: multi-component - Ingenic J4740 Platform Liam Girdwood

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=1281599837.3067.7.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=vapier.adi@gmail.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