From: Vinod Koul <vinod.koul@intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.jf.intel.com>
Cc: Kp Jeeja <jeeja.kp@intel.com>,
alsa-devel@alsa-project.org, broonie@kernel.org,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>,
lgirdwood@gmail.com
Subject: Re: [PATCH 2/2] ASoC: dapm: Add a helper to get the platform for DAPM kcontrol
Date: Mon, 26 May 2014 18:21:46 +0530 [thread overview]
Message-ID: <20140526125146.GE21128@intel.com> (raw)
In-Reply-To: <53833726.9050007@linux.intel.com>
On Mon, May 26, 2014 at 03:44:22PM +0300, Jarkko Nikula wrote:
> On 05/26/2014 03:08 PM, Vinod Koul wrote:
> >From: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
> >
> >commit eee5d7f9 introduced helper for getting codec for DAPM kcontrol, for DSPs
> >we need similar stuff for platforms as well
> >
> Please refer not only the commit id but also commit title ("ASoC:
> dapm: Add a helper to get the CODEC for DAPM kcontrol").
>
> Makes commit log more clear and helps cases where original commit is
> backported to older tree.
ah yes, my bad :(
Mark, do you want a patch or can edit the commit with title "ASoC: dapm: Add a
helper to get the CODEC for DAPM kcontrol" before applying, if no further
comments
--
~Vinod
next prev parent reply other threads:[~2014-05-26 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 12:08 [PATCH 1/2] ASoC: add api for dapm kcontrol configiuration Vinod Koul
2014-05-26 12:08 ` [PATCH 2/2] ASoC: dapm: Add a helper to get the platform for DAPM kcontrol Vinod Koul
2014-05-26 12:44 ` Jarkko Nikula
2014-05-26 12:51 ` Vinod Koul [this message]
2014-05-26 14:29 ` Mark Brown
2014-05-26 13:29 ` Lars-Peter Clausen
2014-05-26 16:23 ` Vinod Koul
2014-05-26 16:52 ` Lars-Peter Clausen
2014-05-26 16:47 ` Vinod Koul
2014-05-26 18:07 ` Lars-Peter Clausen
2014-05-26 18:54 ` Mark Brown
2014-05-26 13:26 ` [PATCH 1/2] ASoC: add api for dapm kcontrol configiuration Lars-Peter Clausen
2014-05-26 15:05 ` Mark Brown
2014-05-26 16:18 ` Vinod Koul
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=20140526125146.GE21128@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@linux.jf.intel.com \
--cc=jeeja.kp@intel.com \
--cc=lgirdwood@gmail.com \
--cc=subhransu.s.prusty@intel.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.