From: Liam Girdwood <lrg@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the sound-asoc tree
Date: Mon, 23 Apr 2012 10:35:38 +0100 [thread overview]
Message-ID: <1335173738.4777.1.camel@odin> (raw)
In-Reply-To: <20120420142850.b276b5fa80e857f8c997e99b@canb.auug.org.au>
On Fri, 2012-04-20 at 14:28 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the sound-asoc tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> In file included from include/trace/ftrace.h:567:0,
> from include/trace/define_trace.h:86,
> from include/trace/events/asoc.h:410,
> from sound/soc/soc-core.c:45:
> include/trace/events/asoc.h: In function 'ftrace_raw_event_snd_soc_dapm_output_path':
> include/trace/events/asoc.h:246:1: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> include/trace/events/asoc.h: In function 'ftrace_raw_event_snd_soc_dapm_input_path':
> include/trace/events/asoc.h:275:1: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
Following fix sent to alsa-devel.
diff --git a/include/trace/events/asoc.h b/include/trace/events/asoc.h
index 6d8efb1..5fc2dcd 100644
--- a/include/trace/events/asoc.h
+++ b/include/trace/events/asoc.h
@@ -263,7 +263,7 @@ TRACE_EVENT(snd_soc_dapm_output_path,
__assign_str(pname, path->name ? path->name : DAPM_DIRECT);
__assign_str(psname, path->sink->name);
__entry->path_connect = path->connect;
- __entry->path_sink = (int)path->sink;
+ __entry->path_sink = (long)path->sink;
),
TP_printk("%c%s -> %s -> %s\n",
@@ -292,7 +292,7 @@ TRACE_EVENT(snd_soc_dapm_input_path,
__assign_str(pname, path->name ? path->name : DAPM_DIRECT);
__assign_str(psname, path->source->name);
__entry->path_connect = path->connect;
- __entry->path_source = (int)path->source;
+ __entry->path_source = (long)path->source;
),
TP_printk("%c%s <- %s <- %s\n",
--
1.7.5.4
next prev parent reply other threads:[~2012-04-23 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 4:28 linux-next: build warnings after merge of the sound-asoc tree Stephen Rothwell
2012-04-23 9:35 ` Liam Girdwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-16 1:36 Stephen Rothwell
2016-05-31 1:43 Stephen Rothwell
2016-05-31 8:16 ` Charles Keepax
2011-04-12 2:05 Stephen Rothwell
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=1335173738.4777.1.camel@odin \
--to=lrg@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).