From: timur@freescale.com (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: fsl: enable ssi clock in probe function
Date: Thu, 29 Mar 2012 11:01:21 -0500 [thread overview]
Message-ID: <4F748751.3020300@freescale.com> (raw)
In-Reply-To: <20120329112949.GM3668@opensource.wolfsonmicro.com>
Mark Brown wrote:
> Applied, thanks (though checking return codes would be nice).
Speaking of return codes, I can't even get ASoC for-3.5 to compile:
/home/b04825/git/linux.ssi-clk/sound/soc/soc-core.c: In function
'soc_bind_dai_link':
/home/b04825/git/linux.ssi-clk/sound/soc/soc-core.c:805:11: error:
'EPROBE_DEFER' undeclared (first use in this function)
/home/b04825/git/linux.ssi-clk/sound/soc/soc-core.c:805:11: note: each
undeclared identifier is reported only once for each function it appears in
/home/b04825/git/linux.ssi-clk/sound/soc/soc-core.c: In function
'soc_check_aux_dev':
/home/b04825/git/linux.ssi-clk/sound/soc/soc-core.c:1346:10: error:
'EPROBE_DEFER' undeclared (first use in this function)
/home/b04825/git/linux.ssi-clk/sound/soc/soc-core.c: In function
'soc_probe_aux_dev':
/home/b04825/git/linux.ssi-clk/sound/soc/soc-core.c:1369:10: error:
'EPROBE_DEFER' undeclared (first use in this function)
/home/b04825/git/linux.ssi-clk/sound/soc/soc-core.c: In function
'soc_check_aux_dev':
/home/b04825/git/linux.ssi-clk/sound/soc/soc-core.c:1347:1: warning:
control reaches end of non-void function
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-03-29 16:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 2:53 [PATCH] ASoC: fsl: enable ssi clock in probe function Shawn Guo
2012-03-29 11:29 ` Mark Brown
2012-03-29 16:01 ` Timur Tabi [this message]
2012-03-29 16:09 ` Shawn Guo
2012-03-29 16:23 ` Timur Tabi
2012-03-29 16:30 ` Mark Brown
2012-03-30 5:55 ` Shawn Guo
2012-03-30 13:03 ` Timur Tabi
2012-03-30 13:16 ` Shawn Guo
2012-03-30 13:19 ` Timur Tabi
2012-03-29 16:30 ` 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=4F748751.3020300@freescale.com \
--to=timur@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).