From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: [PATCH] ASoC: Use bool rather than 1 bit bitfield in multi-component
Date: Thu, 1 Jul 2010 20:55:34 +0100 [thread overview]
Message-ID: <1278014134-19158-1-git-send-email-broonie@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1277407467.3100.579.camel@odin>
This fixes sparse complaints about the bitfield being signed but
only 1 bit wide (so not enough space to store the sign bit).
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
---
include/sound/soc.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/sound/soc.h b/include/sound/soc.h
index b3fe7a8..fb3093b 100644
--- a/include/sound/soc.h
+++ b/include/sound/soc.h
@@ -573,7 +573,7 @@ struct snd_soc_card {
struct list_head list;
struct mutex mutex;
- int instantiated:1;
+ bool instantiated;
int (*probe)(struct platform_device *pdev);
int (*remove)(struct platform_device *pdev);
--
1.7.1
next prev parent reply other threads:[~2010-07-01 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 19:24 [RFC 0/5] ASoC multi-component support : core Liam Girdwood
2010-06-24 21:36 ` Ryan Mallon
2010-06-24 23:12 ` Mark Brown
2010-06-24 23:38 ` Ryan Mallon
2010-06-25 4:51 ` Ryan Mallon
2010-06-25 8:37 ` Liam Girdwood
2010-06-25 22:38 ` Ryan Mallon
2010-06-26 17:52 ` Liam Girdwood
2010-06-26 2:25 ` Wan ZongShun
2010-06-26 17:29 ` Liam Girdwood
2010-06-28 7:16 ` Jarkko Nikula
2010-07-01 19:35 ` Mark Brown
2010-07-01 19:55 ` Mark Brown [this message]
2010-07-05 21:10 ` [PATCH] ASoC: Use bool rather than 1 bit bitfield in multi-component Liam Girdwood
2010-07-01 20:01 ` [RFC 0/5] ASoC multi-component support : core 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=1278014134-19158-1-git-send-email-broonie@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
/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).