All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Bomers <Florian.Bomers@sun.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: snd_ prefix for module options
Date: Tue, 08 Oct 2002 17:48:33 -0700	[thread overview]
Message-ID: <3DA37CE1.760C32F5@sun.com> (raw)
In-Reply-To: 3DA33394.A7C5D9AE@sun.com

Sorry guys, I thought you were talking about the snd_ prefix of the module NAMES
:) for the option names, dropping seems the right thing to do - an error message
should be printed when a snd_* option is used.

Florian


Florian Bomers wrote:
> 
> I like it a lot. Due to the prefix I was able to cleanly remove 0.5.x from my
> system, and we might want to do that later on with 0.9, too :)
> 
> And since I don't see any benefit in removing the prefix - other than cosmetic -
> keeping it will save time for distribution's programmers, sysadmins, writers,
> etc. to update their setup routines, configs, howtos, etc. :)
> 
> Florian
> 
> Takashi Iwai wrote:
> >
> > Hi,
> >
> > so far, all alsa modules use snd_ prefix for each module option.
> > iirc, there was a problem regarding namespace at the time of 2.0
> > kernel, and this was some workaround to avoid confliction.
> > but 2.2 and later kernels have no such a problem at all.
> >
> > so, i'd like to ask you how do you think to remove this snd_ prefix.
> > of course, there is one and only big problem - compatibility!
> >
> > the questions are
> >
> > - whether we should really do it or not?  is it worthy?
> >
> > and
> >
> > - when? now or after 0.9.0-final release?
> >
> > opinions, please?
> >
> > Takashi
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 
> --
> Florian Bomers
> Java Sound
> Java Software/Sun Microsystems, Inc.
> http://java.sun.com/products/java-media/sound/
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel

-- 
Florian Bomers
Java Sound
Java Software/Sun Microsystems, Inc.
http://java.sun.com/products/java-media/sound/


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-10-09  0:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 14:04 snd_ prefix for module options Takashi Iwai
2002-10-08 18:14 ` Peter L Jones
2002-10-08 19:35 ` Florian Bomers
2002-10-09  0:48   ` Florian Bomers [this message]
2002-10-08 22:44 ` Chris Rankin
2002-10-09  6:03   ` Jaroslav Kysela
2002-10-09  8:48     ` Takashi Iwai
2002-10-09  9:02     ` Chris Rankin
2002-10-09 10:33       ` Jaroslav Kysela
2002-10-09  8:47 ` Clemens Ladisch
2002-10-09 10:15 ` Karsten Wiese
2002-10-09 10:19   ` Takashi Iwai
2002-10-09 17:31     ` Jack O'Quin
2002-10-09 17:41     ` Florian Bomers
2002-10-10 11:46       ` Takashi Iwai
2002-10-09 18:37     ` Peter L Jones
2002-10-10 16:11       ` Jack O'Quin
2002-10-10 18:49         ` Peter L Jones
2002-10-10 21:18         ` Florian Bomers
2002-10-11 14:15         ` Takashi Iwai
2002-10-11 19:33           ` Jack O'Quin
2002-10-12  8:56             ` Jaroslav Kysela
2002-10-12 17:22               ` Jack O'Quin

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=3DA37CE1.760C32F5@sun.com \
    --to=florian.bomers@sun.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.