From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
alsa-devel <alsa-devel@alsa-project.org>, lrg <lrg@ti.com>,
"kuninori.morimoto.gx" <kuninori.morimoto.gx@renesas.com>,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH v8 3/3 RESEND] ASoC: da7210: Add support for line input and mic
Date: Mon, 2 Jan 2012 18:55:29 +0530 [thread overview]
Message-ID: <1325510729.12508.33.camel@matrix> (raw)
In-Reply-To: <20120102125815.GI4300@opensource.wolfsonmicro.com>
> Personally I find the versioning information a waste of time in the
> first place, it just obscures more of the subject line in mail readers.
> A patch is going to be considered on its merits no matter how many times
> it's been sent before, having a version number is often just depressing
> (as with those PMIC patches).
OK, let me post it as a new, independent patch.
BTW are you referring to the PMIC patches that one of my colleague (with
same first name) was working on?
next prev parent reply other threads:[~2012-01-02 13:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 12:05 [PATCH v8 3/3 RESEND] ASoC: da7210: Add support for line input and mic Ashish Chavan
2012-01-02 12:00 ` Mark Brown
2012-01-02 12:00 ` [alsa-devel] " Mark Brown
2012-01-02 12:16 ` Ashish Chavan
2012-01-02 12:11 ` Mark Brown
2012-01-02 12:11 ` [alsa-devel] " Mark Brown
2012-01-02 12:40 ` Ashish Chavan
2012-01-02 12:58 ` Mark Brown
2012-01-02 12:58 ` [alsa-devel] " Mark Brown
2012-01-02 13:25 ` Ashish Chavan [this message]
2012-01-02 13:17 ` Mark Brown
2012-01-02 13:17 ` [alsa-devel] " Mark Brown
2012-01-02 14:08 ` Ashish Chavan
-- strict thread matches above, loose matches on Subject: below --
2011-11-01 13:12 Ashish Chavan
2011-11-01 18:55 ` Mark Brown
2011-11-03 8:38 ` Ashish Chavan
2012-01-02 9:17 ` Ashish Chavan
2012-01-02 11:35 ` 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=1325510729.12508.33.camel@matrix \
--to=ashish.chavan@kpitcummins.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=david.chen@diasemi.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.