Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, axel.lin@gmail.com,
	kuninori.morimoto.gx@renesas.com,
	David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH] ASoC: da7210: convert to soc-cache
Date: Wed, 12 Oct 2011 17:06:58 +0530	[thread overview]
Message-ID: <1318419418.12107.187.camel@matrix> (raw)
In-Reply-To: <20111012104708.GG3647@opensource.wolfsonmicro.com>

On Wed, 2011-10-12 at 11:47 +0100, Mark Brown wrote:
> On Wed, Oct 12, 2011 at 03:43:35PM +0530, Ashish Chavan wrote:
> > Hi Axel,
> 
> Don't top post and fix your mail client to thread mails properly; I
> didn't actually see your mail until just now due to the lack of
> threading.
> 

Ooops! I didn't actually realize that.

> > I am thinking of going forward with my posting which is based on current
> > version of da7210 mainline driver. In am ready to take the
> > responsibility of updating(to base it on my patch series) and testing
> > your patch on the hardware that we have.
> 
> > Other option is to wait till your changes gets approved and then base my
> > patch series on updated driver with your changes. But as this may take
> > some time and I definitely want to get more eyes on the patches early,
> > this would be least preferred.
> 
> There's no reason you couldn't do both.

Do you mean I can continue posting the patches to get them reviewed and
update them as per Axel's patch after review part is over?

> 
> I have to be honest here and say that even if I'd seen your mail before
> I applied Axel's patch there's no way I'd have held off on it due to
> your unpublished work.  Axel's patch is here now, is a clear win and
> he's got a strong track record of doing this sort of valuable cleanup
> work.  In contrast you guys have been working for something like a year
> to get the driver for one of your PMICs integrated and haven't yet sent
> any patches for audio at all.  Without a track record of contributions
> it's hard to have confidence that the changes you're proposing will
> arrive when you say, or to have any idea about the level of difficulty
> in integrating them.
> 

I agree with you here. what you are saying is correct as per your
experience. But for da7210 codec, I already have the patch series ready
with some confidence.

  reply	other threads:[~2011-10-12 11:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1102.1318385889.2097.alsa-devel@alsa-project.org>
2011-10-12 10:13 ` [PATCH] ASoC: da7210: convert to soc-cache Ashish Chavan
2011-10-12 10:47   ` Mark Brown
2011-10-12 11:36     ` Ashish Chavan [this message]
2011-10-12 12:10       ` Mark Brown
2011-10-12 12:32         ` Ashish Chavan
2011-10-13  5:34   ` Kuninori Morimoto
2011-10-11 23:16 Axel Lin
2011-10-12 10:25 ` 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=1318419418.12107.187.camel@matrix \
    --to=ashish.chavan@kpitcummins.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=axel.lin@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=david.chen@diasemi.com \
    --cc=kuninori.morimoto.gx@renesas.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