All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [alsa-devel] [PATCH 0/4] ASOC: Add AM3517 EVM support in ASOC
Date: Wed, 3 Feb 2010 17:51:02 -0800	[thread overview]
Message-ID: <20100204015102.GO22747@atomide.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB031E4F20BB@dbde02.ent.ti.com>

* Aggarwal, Anuj <anuj.aggarwal@ti.com> [100129 00:13]:
> > -----Original Message-----
> > From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]
> > Sent: Friday, October 30, 2009 4:00 AM
> > To: Aggarwal, Anuj
> > Cc: alsa-devel@alsa-project.org; linux-omap@vger.kernel.org;
> > tony@atomide.com
> > Subject: Re: [alsa-devel] [PATCH 0/4] ASOC: Add AM3517 EVM support in ASOC
> > 
> > On Fri, Oct 30, 2009 at 12:22:17AM +0530, Anuj Aggarwal wrote:
> > > This patch series add support for OMAP3517 / AM3517 EVM in ASOC.
> > > It also enables the required drivers - I2C and McBSP, along with
> > > Alsa SoC subsystem, in the default configuration for the EVM.
> > >
> > > Anuj Aggarwal (4):
> > >   Audio: Adding OMAP3517 / AM3517 EVM support in ASOC
> > >   Audio: Modifying Kconfig/Makefile for AM3517 EVM
> > >   Audio: Modifying board-evm file for audio codec
> > >   Audio: Modifying the defconfig for OMAP3517 / AM3517 EVM
> > 
> > These all look good - I've applied patches 1 and 2 to ASoC, patches 3
> > and 4 should go via OMAP and are
> Tony,
> 
> I could not find patches 3 & 4 on l-o master. Am I looking at the right 
> branch?

Hmm, well I still have about 70 patches pending and have
not yet gotten into looking at the board-*.c files that much..

But looks like I had marked these as "awaiting upstream".
I've marked them "new" again and will queue into omap for-next
when I get to dealing with the board-*.c files.

BTW, I assume these two patches are the missing ones:

http://patchwork.kernel.org/patch/56501/
http://patchwork.kernel.org/patch/56502/

Regards,

Tony

 
> > 
> > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > 
> > if it helps (or even if it doesn't!).  Thanks.
> 

  reply	other threads:[~2010-02-04  1:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 18:52 [PATCH 0/4] ASOC: Add AM3517 EVM support in ASOC Anuj Aggarwal
2009-10-29 22:29 ` [alsa-devel] " Mark Brown
2010-01-29  8:16   ` Aggarwal, Anuj
2010-02-04  1:51     ` Tony Lindgren [this message]
2010-02-04  8:11       ` [alsa-devel] " Aggarwal, Anuj
2010-02-05  0:04       ` Tony Lindgren

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=20100204015102.GO22747@atomide.com \
    --to=tony@atomide.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=anuj.aggarwal@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.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.