From: Stas Sergeev <stsp@aknet.ru>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: [patch] snd-pcsp: depend on CONFIG_EXPERIMENTAL
Date: Sat, 17 May 2008 02:14:12 +0400 [thread overview]
Message-ID: <482E0734.7080003@aknet.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
Hello.
Considering all the feedbacks I got,
depending snd-pcsp on CONFIG_EXPERIMENTAL
looks like the only safe way to get out
of all the troubles at one go. :)
Can the attached patch be applied?
Btw, it seems to me that the alsa-kernel
hg tree somehow lacks a few snd-pcsp patches
that the alsa git tree has... how have that
happened and how can be fixed?
[-- Attachment #2: pcsp_exp.diff --]
[-- Type: text/x-patch, Size: 642 bytes --]
# HG changeset patch
# User Stas Sergeev <stsp@users.sourceforge.net>
# Date 1210975452 -14400
# Node ID 49d310de8ac42e5c495cf39440f4fde307b39c75
# Parent 3887126bbd9ca422208e651d46f9f5385d409efe
snd-pcsp: depend on CONFIG_EXPERIMENTAL
Signed-off-by: Stas Sergeev <stsp@aknet.ru>
diff -r 3887126bbd9c -r 49d310de8ac4 drivers/Kconfig
--- a/drivers/Kconfig Fri May 16 22:01:53 2008 +0400
+++ b/drivers/Kconfig Sat May 17 02:04:12 2008 +0400
@@ -6,6 +6,7 @@ menu "Generic devices"
config SND_PCSP
tristate "Internal PC speaker support"
+ depends on EXPERIMENTAL
depends on X86_PC && HIGH_RES_TIMERS
depends on INPUT
depends on SND
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2008-05-16 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 22:14 Stas Sergeev [this message]
2008-05-17 6:52 ` [patch] snd-pcsp: depend on CONFIG_EXPERIMENTAL Takashi Iwai
2008-05-17 8:01 ` Rene Herman
2008-05-17 13:50 ` Takashi Iwai
2008-05-17 9:05 ` Adrian Bunk
2008-05-17 10:45 ` Stas Sergeev
2008-05-17 11:33 ` Adrian Bunk
2008-05-17 16:01 ` Rene Herman
2008-05-18 5:57 ` Lee Revell
2008-05-18 8:01 ` 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=482E0734.7080003@aknet.ru \
--to=stsp@aknet.ru \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.