From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Anuj Aggarwal <anuj.aggarwal@ti.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: am3517evm: Remove unused cpu_dai from hw_params
Date: Tue, 11 Sep 2012 08:21:16 +0800 [thread overview]
Message-ID: <20120911002115.GF30699@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1347281717-10244-1-git-send-email-peter.ujfalusi@ti.com>
On Mon, Sep 10, 2012 at 03:55:17PM +0300, Peter Ujfalusi wrote:
> cpu_dai is not in use in this function and just generates warning at
> compile time.
Applied, thanks.
> Commit: fca04ae ASoC: am3517evm: Do not configure McBSP1 CLKR/FSR signal muxing
> left this line in the code which generates now warning.
Please just include stuff like this in the changelog.
prev parent reply other threads:[~2012-09-11 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 12:55 [PATCH] ASoC: am3517evm: Remove unused cpu_dai from hw_params Peter Ujfalusi
2012-09-11 0:21 ` Mark Brown [this message]
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=20120911002115.GF30699@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@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 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).