From: "Jack O'Quin" Subject: Re: snd_ prefix for module options Date: 11 Oct 2002 14:33:48 -0500 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <87ptugepnn.fsf@sulphur.joq.us> References: <200210091937.05652@advent.drealm.org.uk> <87u1juxoit.fsf@sulphur.joq.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Takashi Iwai Cc: Peter L Jones , Karsten Wiese , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org > Jack O'Quin wrote: > > Can someone please explain what terrible problem we're trying to solve > > that justifies introducing *any* breakage at all? > > > ALSA is part of the 2.5 kernel now. It is mainstream Linux software, > > good technology, needed by many users. Isn't it about time to start > > thinking and acting that way? Takashi Iwai writes: > this is the very reason why "now" i asked. > since the ALSA is now on the official kernel tree, we must follow to > the standard rules, too. and the snd_ prefix is obviously ugly from > this perspective. > > if we live alone as external, then we don't have to care - we could do > as we like. but the mainstream means that such exception has to be > excluded, too, at least before 2.5 turns into the "real mainstream", > i.e. 2.6 (or 3.0). Are you saying that the "snd_" prefix violates standard Linux kernel rules for device driver options? Did the kernel developers request this change? If so, I withdraw my objection. I thought the change was merely cosmetic. :-) Regards, -- Jack O'Quin Austin, Texas, USA ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf