public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@redhat.com>, "J.A. Magallon" <jamagallon@able.es>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Christoph Hellwig <hch@ns.caldera.de>,
	Jaroslav Kysela <perex@suse.cz>,
	sound-hackers@zabbo.net, linux-sound@vger.rutgers.edu,
	linux-kernel@vger.kernel.org
Subject: Re: [s-h] Re: ALSA patch for 2.5.2pre9 kernel
Date: Tue, 8 Jan 2002 10:30:46 +0100	[thread overview]
Message-ID: <20020108103046.A3545@werewolf.able.es> (raw)
In-Reply-To: <20020108102833.A2927@werewolf.able.es>
In-Reply-To: <20020108102833.A2927@werewolf.able.es>; from jamagallon@able.es on Tue, Jan 08, 2002 at 10:28:33 +0100


On 20020108 Linus Torvalds wrote:
>
>On Mon, 7 Jan 2002, Alan Cox wrote:
>> > Would't it be better to split drivers:
>> >
>> > sound/core.c
>> > sound/alsa/alsa-core.c
>> > sound/alsa/drivers/alsa-emu10k.c
>> > sound/oss/oss-core.c
>> > sound/oss/drivers/oss-emu10k.c
>>
>> Thats much harder to do randomg greps on and to find stuff,than drivers
>> first
>
>I agree. Put drivers separately, let's not split it up more than that.
>

What would you do with drivers with the same name (source code file)
in alsa and oss ?
Sound is special because you have two implementations of the same subsystem
living together. And eventually in a (near?) future, the oss subtree
will be killed and the alsa one would go up one level, just as is. Much
cleaner. And you will end with

sound/alsa-core.c
sound/drivers/alsa-driver.c

By

/juan

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.18-pre2-beo #1 SMP Tue Jan 8 03:18:18 CET 2002 i686

       reply	other threads:[~2002-01-08  9:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020108102833.A2927@werewolf.able.es>
2002-01-08  9:30 ` J.A. Magallon [this message]
2002-01-08  9:52   ` [s-h] Re: ALSA patch for 2.5.2pre9 kernel Abramo Bagnara
2002-01-08 10:12     ` Takashi Iwai
2002-01-08 10:18       ` Jaroslav Kysela
2002-01-08 10:34         ` Takashi Iwai
2002-01-08 10:36         ` Abramo Bagnara
2002-01-08 10:50           ` Jaroslav Kysela
2002-01-08 10:28       ` Abramo Bagnara
2002-01-08 10:41         ` Jaroslav Kysela
2002-01-07 23:44 J.A. Magallon
2002-01-08  2:01 ` [s-h] " Alan Cox
2002-01-08  5:12   ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2002-01-07 20:51 Steven Walter
2002-01-07 19:03 Dimitrie Paun
2002-01-07 18:10 Arnaldo Carvalho de Melo
2002-01-08  2:13 ` [s-h] " Alan Cox
2002-01-08 12:47   ` Arnaldo Carvalho de Melo
2002-01-07 18:00 Linus Torvalds
2002-01-07 18:19 ` [s-h] " Abramo Bagnara
2002-01-07 18:29   ` Linus Torvalds
2002-01-07 18:39     ` Abramo Bagnara
2002-01-07 18:47       ` Linus Torvalds
2002-01-07 19:09         ` Abramo Bagnara
2002-01-07 19:21         ` Pozsar Balazs
2002-01-07 20:29         ` Jauder Ho
2002-01-14  3:10         ` Pavel Machek
2002-01-07 21:25   ` Christoph Hellwig
2002-01-08  1:16     ` Timothy Covell
2002-01-08  2:53     ` Miles Lane

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=20020108103046.A3545@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alan@redhat.com \
    --cc=hch@ns.caldera.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.rutgers.edu \
    --cc=perex@suse.cz \
    --cc=sound-hackers@zabbo.net \
    --cc=torvalds@transmeta.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox