From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [asoc:topic/cs4271 37/37] include/sound/cs4271.h:22:31: sparse: dubious one-bit signed bitfield
Date: Sat, 06 Oct 2012 16:54:30 +0000 [thread overview]
Message-ID: <20121006165430.GA19636@localhost> (raw)
Hi Daniel,
FYI, there are new sparse warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git topic/cs4271
head: d24f7344f8f3e6853d128d43b13424b6734d8211
commit: d24f7344f8f3e6853d128d43b13424b6734d8211 [37/37] ASoC: cs4271: add support for AMUTEB=BMUTEC feature
+ include/sound/cs4271.h:22:31: sparse: dubious one-bit signed bitfield
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
reply other threads:[~2012-10-06 16:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121006165430.GA19636@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.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