From: Martin Sandsmark <martin.sandsmark@kde.org>
To: alsa-devel@alsa-project.org
Subject: [PATCH] Removing an assert
Date: Thu, 05 Jul 2012 09:55:23 +0200 [thread overview]
Message-ID: <1381041.X9jejKqOkf@malacandra> (raw)
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
Hi!
There is an assert in snd_hctl_handle_event in alsa-lib that gets triggered on
every login for many KDE users. From what I can see it is superflous, and gets
triggered because the device in an event has gone away. This case is handled
just beneath the assert as well, and I therefore don't see the reason for this
assert at all.
Entry in bug tracker:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5471
--
Martin Sandsmark
[-- Attachment #2: 0001-Remove-a-useless-assert.patch --]
[-- Type: text/x-patch, Size: 934 bytes --]
>From dff3de9705eb617b619251c2aec30d5ca9c13046 Mon Sep 17 00:00:00 2001
From: Martin Sandsmark <martin.sandsmark@kde.org>
Date: Thu, 5 Jul 2012 09:40:07 +0200
Subject: [PATCH] Remove a useless assert.
The case where the element is unavailable (for example gone away since
the event was created) is handled beneath.
See also bug 5471.
---
src/control/hcontrol.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/src/control/hcontrol.c b/src/control/hcontrol.c
index 8ffc434..ee1d907 100644
--- a/src/control/hcontrol.c
+++ b/src/control/hcontrol.c
@@ -761,7 +761,6 @@ static int snd_hctl_handle_event(snd_hctl_t *hctl, snd_ctl_event_t *event)
if (event->data.elem.mask & (SNDRV_CTL_EVENT_MASK_VALUE |
SNDRV_CTL_EVENT_MASK_INFO)) {
elem = snd_hctl_find_elem(hctl, &event->data.elem.id);
- assert(elem);
if (!elem)
return -ENOENT;
res = snd_hctl_elem_throw_event(elem, event->data.elem.mask &
--
1.7.11.1
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2012-07-05 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 7:55 Martin Sandsmark [this message]
2012-07-05 8:09 ` [PATCH] Removing an assert Takashi Iwai
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=1381041.X9jejKqOkf@malacandra \
--to=martin.sandsmark@kde.org \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.