From: Fengguang Wu <fengguang.wu@intel.com>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
kernel-janitors@vger.kernel.org
Subject: [asoc:for-next 110/115] sound/soc/soc-core.c:901 soc_bind_dai_link() error: we previously assumed 'dai_link->platform_of_node' could be null (see line 887)
Date: Tue, 11 Sep 2012 11:00:03 +0800 [thread overview]
Message-ID: <20120911030003.GB23365@localhost> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
head: bffb28a4233d25d37a444785f766e98a041b4413
commit: a6179d2741640a1ec88a1c5b9c2c28bdf45666db [110/115] ASoC: core: display the platform node name if there is no platform name
All smatch warnings:
+ sound/soc/soc-core.c:901 soc_bind_dai_link() error: we previously assumed 'dai_link->platform_of_node' could be null (see line 887)
vim +901 sound/soc/soc-core.c
884
885 /* find one from the set of registered platforms */
886 list_for_each_entry(platform, &platform_list, list) {
> 887 if (dai_link->platform_of_node) {
888 if (platform->dev->of_node !=
889 dai_link->platform_of_node)
890 continue;
891 } else {
892 if (strcmp(platform->name, platform_name))
893 continue;
894 }
895
896 rtd->platform = platform;
897 }
898 if (!rtd->platform) {
899 dev_err(card->dev, "platform %s not registered\n",
900 dai_link->platform_name ? :
> 901 dai_link->platform_of_node->full_name);
902 return -EPROBE_DEFER;
903 }
904
905 card->num_rtd++;
906
907 return 0;
908 }
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
next reply other threads:[~2012-09-11 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 3:00 Fengguang Wu [this message]
2012-09-11 3:26 ` [asoc:for-next 110/115] sound/soc/soc-core.c:901 soc_bind_dai_link() error: we previously assumed 'dai_link->platform_of_node' could be null (see line 887) 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=20120911030003.GB23365@localhost \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=timur@freescale.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).