public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [RFC 0/2 rev2] McBSP and ASoC OMAP update patches for 2430 and 34xx
Date: Mon, 8 Sep 2008 17:48:58 -0700	[thread overview]
Message-ID: <20080909004858.GJ29054@atomide.com> (raw)
In-Reply-To: <1220869784-16607-1-git-send-email-jarkko.nikula@nokia.com>

* Jarkko Nikula <jarkko.nikula@nokia.com> [080908 03:30]:
> Here is second version of patch adding support for 2430 in McBSP driver.
> Updated version uses phys_base instead of virt_base. See following commits from Russell King:
> 
> ecec3b3e080464cc1b4e792cf4d8e7e89d50b011
> 2cfd6fcda3b8c6ee7a5fa9a4573e3246532a0716
> 
> Second patch is the same than first version. It's for testing ASoC OMAP
> and eventually it will go through the alsa-devel.

Thanks, pushing these to l-o tree.

Tony

  reply	other threads:[~2008-09-09  0:49 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 11:55 [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx Jarkko Nikula
2008-08-21 11:55 ` [RFC] ARM: OMAP: Add support for OMAP2430 in McBSP Jarkko Nikula
2008-08-21 11:55 ` [RFC] ASoC: OMAP: Add support for OMAP2430 and OMAP34xx in McBSP DAI driver Jarkko Nikula
2008-08-21 21:51 ` [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx Steve Sakoman
2008-08-22  7:57   ` Jarkko Nikula
2008-08-25 19:19     ` Steve Sakoman
2008-08-25 19:29       ` Felipe Balbi
2008-08-25 21:35       ` Felipe Balbi
2008-08-25 21:39         ` Felipe Balbi
2008-08-25 21:50         ` Steve Sakoman
2008-08-25 21:53           ` Felipe Balbi
2008-08-25 22:13             ` Steve Sakoman
2008-08-25 22:30             ` Steve Sakoman
2008-08-25 22:40               ` Felipe Balbi
2008-08-25 22:54                 ` Felipe Balbi
2008-08-25 23:34                   ` Steve Sakoman
2008-08-26  0:08                     ` Felipe Balbi
2008-08-26 13:19       ` Jarkko Nikula
2008-08-26 14:23         ` Steve Sakoman
2008-08-26 17:18         ` Steve Sakoman
2008-08-27  6:38           ` Jarkko Nikula
2008-08-27 13:39             ` Steve Sakoman
2008-08-27 20:57               ` Steve Sakoman
2008-08-27 21:25                 ` Koen Kooi
2008-08-27 22:14                   ` Steve Sakoman
2008-08-28 11:03                 ` Jarkko Nikula
2008-08-23 11:32 ` Arun KS
2008-09-05  1:12 ` Tony Lindgren
2008-09-05  6:18   ` Steve Sakoman
2008-09-05 16:56     ` Tony Lindgren
2008-09-05 17:23       ` Steve Sakoman
2008-09-05 17:52         ` Tony Lindgren
2008-09-08 10:29       ` [RFC 0/2 rev2] " Jarkko Nikula
2008-09-09  0:48         ` Tony Lindgren [this message]
2008-09-08 10:29       ` [RFC rev2] ARM: OMAP: Add support for OMAP2430 in McBSP Jarkko Nikula
2008-09-08 10:29       ` [RFC rev2] ASoC: OMAP: Add support for OMAP2430 and OMAP34xx in McBSP DAI driver Jarkko Nikula
2008-09-20 11:22     ` [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx Arun KS
2008-09-20 11:41       ` Koen Kooi
2008-09-20 12:03         ` Arun KS
     [not found]         ` <dfeb90390809200453i35da7891lcea6d620dbb0e46a@mail.gmail.com>
2008-09-20 12:21           ` Koen Kooi

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=20080909004858.GJ29054@atomide.com \
    --to=tony@atomide.com \
    --cc=jarkko.nikula@nokia.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