From: janani-sankarababu <jananis37@gmail.com>
To: eric@anholt.net
Cc: stefan.wahren@i2se.com, gregkh@linuxfoundation.org,
f.fainelli@gmail.com, rjui@broadcom.com, sbranden@broadcom.com,
aishpant@gmail.com, mzoran@crowfest.net, julia.lawall@lip6.fr,
vicmos89@gmail.com, sreyamittal5@gmail.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
janani-sankarababu <jananis37@gmail.com>
Subject: [PATCH] Staging: vc04_services: Fix WARN_ON instead of BUG_ON
Date: Mon, 31 Jul 2017 12:44:03 +0530 [thread overview]
Message-ID: <1501485243-11977-1-git-send-email-jananis37@gmail.com> (raw)
This patch is to replace the use of BUG_ON macro with WARN_ON
inorder to prevent the crashing of the kernel.
Signed-off-by: Janani Sankara Babu <jananis37@gmail.com>
---
drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c b/drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c
index f484bb0..30bc246 100644
--- a/drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c
+++ b/drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c
@@ -91,7 +91,7 @@ static int snd_bcm2835_ctl_get(struct snd_kcontrol *kcontrol,
if (mutex_lock_interruptible(&chip->audio_mutex))
return -EINTR;
- BUG_ON(!chip && !(chip->avail_substreams & AVAIL_SUBSTREAMS_MASK));
+ WARN_ON(!chip && !(chip->avail_substreams & AVAIL_SUBSTREAMS_MASK));
if (kcontrol->private_value == PCM_PLAYBACK_VOLUME)
ucontrol->value.integer.value[0] = chip2alsa(chip->volume);
--
1.9.1
next reply other threads:[~2017-07-31 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 7:14 janani-sankarababu [this message]
2017-07-31 8:10 ` Stefan Wahren
2017-07-31 8:45 ` Dan Carpenter
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=1501485243-11977-1-git-send-email-jananis37@gmail.com \
--to=jananis37@gmail.com \
--cc=aishpant@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mzoran@crowfest.net \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=sreyamittal5@gmail.com \
--cc=stefan.wahren@i2se.com \
--cc=vicmos89@gmail.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
all inboxes | Powered by JetHome®