public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Cai, Cliff" <Cliff.Cai@analog.com>
Cc: Cliff Cai <cliffcai.sh@gmail.com>,
	Mike Frysinger <vapier.adi@gmail.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org" 
	<device-drivers-devel@blackfin.uclinux.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [alsa-devel] [Device-drivers-devel] [PATCH] Add driver for Analog Devices ADAU1701 SigmaDSP
Date: Mon, 14 Mar 2011 11:29:47 +0000	[thread overview]
Message-ID: <20110314112946.GA2626@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <DB904C5425BA6F4E8424B3B51A1414D16649F4AB9D@NWD2CMBX1.ad.analog.com>

On Sun, Mar 13, 2011 at 10:23:19PM -0400, Cai, Cliff wrote:

> I think I need to have a check of the requirement from customer.
> Anyway,if I modified the driver according to the comments here,
> Would you like to accept it currently or we need to wait until the missing patch
> Has been merged in mainline?

Please repost, there were quite a few issues raised with this revision
even outside the firmware.  For the purpose of getting things into
mainline I'd recommend splitting out the functionaltiy which allows
firmware to be loaded dynamically at runtime as a second patch.

  reply	other threads:[~2011-03-14 11:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07  1:11 [PATCH] Add driver for Analog Devices ADAU1701 SigmaDSP cliff.cai
2011-03-07  2:44 ` [Device-drivers-devel] " Mike Frysinger
2011-03-07 11:44   ` [alsa-devel] " Mark Brown
2011-03-07 11:01 ` [alsa-devel] " Liam Girdwood
2011-03-07 11:41 ` Mark Brown
2011-03-07 11:50   ` [Device-drivers-devel] " Mike Frysinger
2011-03-07 12:15     ` Mark Brown
2011-03-07 12:29       ` Mike Frysinger
2011-03-07 14:59         ` Mark Brown
2011-03-07 15:33           ` Mike Frysinger
2011-03-07 15:55             ` Mark Brown
2011-03-09  6:08               ` Mike Frysinger
2011-03-09  7:39                 ` [alsa-devel] " Cliff Cai
2011-03-09  9:55                 ` Mark Brown
2011-04-19  0:15           ` Andres Salomon
2011-04-19  8:06             ` Mark Brown
2011-03-09  7:25         ` [alsa-devel] " Cliff Cai
2011-03-09 10:00           ` Mark Brown
2011-03-10  0:35             ` Mike Frysinger
2011-03-10  9:45             ` Cai, Cliff
2011-03-10 13:46               ` Mark Brown
2011-03-11  7:54                 ` Cai, Cliff
2011-03-11 11:53                   ` Mark Brown
2011-03-14  2:23                     ` Cai, Cliff
2011-03-14 11:29                       ` Mark Brown [this message]
2011-03-09  7:04   ` [alsa-devel] " Cliff Cai
2011-03-09 10:12     ` Mark Brown
2011-03-10 10:04       ` Cai, Cliff

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=20110314112946.GA2626@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=Cliff.Cai@analog.com \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=cliffcai.sh@gmail.com \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --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