public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Some patches need reposting, inbox cleared, patchwork cleared
Date: Mon, 16 Nov 2009 12:59:48 -0800	[thread overview]
Message-ID: <20091116205948.GQ3684@atomide.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB030A8C8C3A@dbde02.ent.ti.com>

* Aggarwal, Anuj <anuj.aggarwal@ti.com> [091116 03:37]:
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> > owner@vger.kernel.org] On Behalf Of Tony Lindgren
> > Sent: Saturday, November 14, 2009 6:38 AM
> > To: Pandita, Vikram
> > Cc: linux-omap@vger.kernel.org
> > Subject: Re: Some patches need reposting, inbox cleared, patchwork cleared
> > 
> > * Pandita, Vikram <vikram.pandita@ti.com> [091113 11:06]:
> > > Tony
> > >
> > > >-----Original Message-----
> > > >From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> > owner@vger.kernel.org] On Behalf Of
> > > >Pandita, Vikram
> > > >>From: Tony Lindgren [mailto:tony@atomide.com]
> > > >>> I just verified booting zoom3 on l-o master, and its working fine.
> > > >>
> > > >>OK good. Can you also try booting this patch from Felipe on 3630:
> > > >>
> > > >>http://patchwork.kernel.org/patch/59540/
> > > >
> > > >Patch does not apply. Rebasing now and testing.
> > >
> > > Rebased Patch (attached) boots up fine now on 3630 Zoom3 board.
> > >
> > > Logs:
> > > CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
> > > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
> > > Machine: OMAP Zoom3 board
> > > Memory policy: ECC disabled, Data cache writeback
> > > OMAP3630 ES1.0 (l2cache iva sgx neon isp )
> > >
> > 
> > OK, thanks applying it.
> Tony,
> 
> I am not able to see the following patch in the list:
> 
> OMAP3EVM: Use the twl4030_setup_data for headset pop-removal
> http://marc.info/?l=linux-omap&m=125368984011630&w=2
> 
> Can you apply it please?

It looks like it should go in via the ASoC, so not taking it.

>From MAINTAINERS file:

SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEMENT (ASoC)
M:      Liam Girdwood <lrg@slimlogic.co.uk>
M:      Mark Brown <broonie@opensource.wolfsonmicro.com>
T:      git git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git
L:      alsa-devel@alsa-project.org (moderated for non-subscribers)
W:      http://alsa-project.org/main/index.php/ASoC
S:      Supported
F:      sound/soc/
F:      include/sound/soc*

Regards,

Tony

  reply	other threads:[~2009-11-16 20:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  0:38 Some patches need reposting, inbox cleared, patchwork cleared Tony Lindgren
2009-11-13  4:41 ` Gadiyar, Anand
2009-11-13  4:44   ` Gadiyar, Anand
2009-11-13 18:03     ` Tony Lindgren
2009-11-13 18:06       ` Pandita, Vikram
2009-11-13 18:15         ` Tony Lindgren
2009-11-13 18:20           ` Pandita, Vikram
2009-11-13 19:07             ` Pandita, Vikram
2009-11-14  1:08               ` Tony Lindgren
2009-11-16 11:37                 ` Aggarwal, Anuj
2009-11-16 20:59                   ` Tony Lindgren [this message]
2009-11-13 18:29       ` Gadiyar, Anand

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=20091116205948.GQ3684@atomide.com \
    --to=tony@atomide.com \
    --cc=anuj.aggarwal@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox