From: Mike Frysinger <vapier@gentoo.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Scott Jiang <scott.jiang@analog.com>,
alsa-devel@alsa-project.org, Cliff Cai <cliff.cai@analog.com>,
device-drivers-devel@blackfin.uclinux.org,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [Device-drivers-devel] [PATCH] ASoC: ad74111: new codec driver
Date: Mon, 28 Mar 2011 03:22:11 -0400 [thread overview]
Message-ID: <AANLkTincrRKARvVwuJe52VA26AZHeDsN9sWWnrBNXeyf@mail.gmail.com> (raw)
In-Reply-To: <20110327134343.GA6292@opensource.wolfsonmicro.com>
On Sun, Mar 27, 2011 at 09:43, Mark Brown wrote:
> - Follow up promptly on reviews - I'm rarely seeing updates to patches
> that involve any domain specific changes, and where there is followup
> it's often at the next release. This interacts badly with the
> submission against old code issues as that means you're likely to
> require some fairly straightforward API updates but waiting to
> resubmit means that you'll often end up requiring further updates
> next time around.
>
> For example, the SSM2604 driver you're submitting now was originally
> sent last August and you sent patches for ADAV801/3, ADAU1361, ADAU1381
> and ADAU1761 at the end of last year which mostly just needed fairly
> straightforward updates for old kernel issues but which haven't been
> resubmitted since. None of these devices look like they should be hard
> to get support integrated into mainline but the above issues are making
> that harder work than it needs to be.
atm, it's basically lack of developer time. technically, ADI codecs
are no longer my job (they were marginally so in the past). i do any
updates that i can slap together in my off time, but as soon as you
start talking about real issues (such as exposing registers or
programming the part differently), it's beyond my experience. most of
the TLA's you throw around i have to look up ;).
so basically yes, i agree it's currently screwed up.
-mike
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2011-03-28 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 8:33 [PATCH] ASoC: ad74111: new codec driver Mike Frysinger
2011-03-26 12:21 ` Mark Brown
2011-03-26 17:52 ` [Device-drivers-devel] " Mike Frysinger
2011-03-26 18:09 ` Mark Brown
2011-03-27 4:10 ` Mike Frysinger
2011-03-27 13:43 ` Mark Brown
2011-03-28 7:22 ` Mike Frysinger [this message]
2011-03-29 21:28 ` Mark Brown
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=AANLkTincrRKARvVwuJe52VA26AZHeDsN9sWWnrBNXeyf@mail.gmail.com \
--to=vapier@gentoo.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cliff.cai@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=lrg@slimlogic.co.uk \
--cc=scott.jiang@analog.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;
as well as URLs for NNTP newsgroup(s).