From: Rene Herman <rene.herman@keyaccess.nl>
To: Stas Sergeev <stsp@aknet.ru>
Cc: Takashi Iwai <tiwai@suse.de>, Adrian Bunk <bunk@kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: [patch] snd-pcsp: depend on CONFIG_EXPERIMENTAL
Date: Sat, 17 May 2008 18:01:33 +0200 [thread overview]
Message-ID: <482F015D.8030504@keyaccess.nl> (raw)
In-Reply-To: <482EB747.6040103@aknet.ru>
On 17-05-08 12:45, Stas Sergeev wrote:
>> No objections against your patch, but considering that virtually
>> everyone has EXPERIMENTAL enabled in his kernel it won't bring
>> you out of any troubles...
> So do you think it should depend
> on CONFIG_BROKEN?
No, I wouldn't do that. It isn't all that broken it would seem (assuming
it will work for me after applying the patch you posted that should
make it work with older alsa-lib; haven't checked yet).
> The other possibilities, like hardcoding
> the index value as Andreas Mohr suggested,
> are also interesting. Can someone please
> comment if this is acceptable?
Generally I'd say totally unacceptable but this might in fact be a
special case due to it being generic PC hardware and expected to be
present therefore -- it might actually make some sense to reserve a
#define SND_INDEX_PCSP MAXINT or some such so that this thing gets a
stable index (and make sure people know to select it through its name
like in "default:pcsp" and the like). I'd ask Takashi for comment on that...
Rene.
next prev parent reply other threads:[~2008-05-17 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 22:14 [patch] snd-pcsp: depend on CONFIG_EXPERIMENTAL Stas Sergeev
2008-05-17 6:52 ` 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 [this message]
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=482F015D.8030504@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@kernel.org \
--cc=stsp@aknet.ru \
--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.