public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: broonie@kernel.org, lgirdwood@gmail.com,
	alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
	sfr@canb.auug.org.au
Subject: Re: [PATCH] ASoC: arizona: Add data structure for voice trigger notifier
Date: Tue, 31 May 2016 13:58:53 +0200	[thread overview]
Message-ID: <26834776.a9zKDjMD7P@wuerfel> (raw)
In-Reply-To: <1464695057-11723-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>

On Tuesday, May 31, 2016 12:44:17 PM CEST Charles Keepax wrote:
> 64-bit builds would generate a warning when we passed the core number as
> a pointer through the notifier data:
> 
> sound/soc/codecs/cs47l24.c:1091:13: warning: cast to pointer from
> integer of different size [-Wint-to-pointer-cast]
>              (void *)i);
> 
> Rather than just fix this up with more casting add a data structure that
> holds information for the notifier chain. This will make it easier to
> add additional information in the future as well.
> 
> Fixes: 7baa7e2490e1 ("ASoC: arizona: Add event notification on voice trigger events")
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com> 

Thanks for addressing it so quickly!

Acked-by: Arnd Bergmann <arnd@arndb.de>

  reply	other threads:[~2016-05-31 11:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 11:44 [PATCH] ASoC: arizona: Add data structure for voice trigger notifier Charles Keepax
2016-05-31 11:58 ` Arnd Bergmann [this message]
2016-05-31 17:46 ` Applied "ASoC: arizona: Add data structure for voice trigger notifier" to the asoc tree 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=26834776.a9zKDjMD7P@wuerfel \
    --to=arnd@arndb.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=lgirdwood@gmail.com \
    --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