From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Chavan <ashish.chavan@kpitcummins.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 13:10:04 +0100 [thread overview]
Message-ID: <20111012121004.GJ3647@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318419418.12107.187.camel@matrix>
On Wed, Oct 12, 2011 at 05:06:58PM +0530, Ashish Chavan wrote:
> 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?
Well, if there's conflicts with Axel's patches obviously that'll be a
review issue. But in general talking about doing patches isn't really
useful.
next prev parent reply other threads:[~2011-10-12 12:10 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
2011-10-12 12:10 ` Mark Brown [this message]
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=20111012121004.GJ3647@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ashish.chavan@kpitcummins.com \
--cc=axel.lin@gmail.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