public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	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: ALSA patch for 2.5.2pre9 kernel
Date: Tue, 8 Jan 2002 00:44:16 +0100	[thread overview]
Message-ID: <20020108004416.A23665@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.33.0201070858150.6450-100000@penguin.transmeta.com> <E16Ndc4-0001sW-00@the-village.bc.nu>
In-Reply-To: <E16Ndc4-0001sW-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Jan 07, 2002 at 18:31:08 +0100


On 20020107 Alan Cox wrote:
>
>so by that logic we'd have
>
>	sound/soundcore.c
>	sound/alsa/alsalibcode
>	sound/oss/osscore
>
>	sound/drivers/cardfoo.c
>

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

low level card drivers are different, and this way oss and alsa are
independent subtrees.

BTW, 2.5.x was born to be broken, so this is the moment to reorganize
the beast (better before than after kbuild 2.5 ?)

By

-- 
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-pre1-beo #1 SMP Fri Jan 4 02:25:59 CET 2002 i686

  parent reply	other threads:[~2002-01-07 23:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06 17:39 ALSA patch for 2.5.2pre9 kernel Jaroslav Kysela
2002-01-07 14:32 ` Christoph Hellwig
2002-01-07 15:41   ` David Weinehall
2002-01-07 17:18     ` Jaroslav Kysela
2002-01-07 17:02   ` Linus Torvalds
2002-01-07 17:06     ` Christoph Hellwig
2002-01-07 17:25       ` Jaroslav Kysela
2002-01-07 17:22     ` Dave Jones
2002-01-07 17:31     ` Alan Cox
2002-01-07 18:00       ` Linus Torvalds
2002-01-07 18:10         ` Arnaldo Carvalho de Melo
2002-01-07 18:38           ` Sebastian Dröge
2002-01-07 21:32             ` Thierry Vignaud
2002-01-08  2:13           ` [s-h] " Alan Cox
2002-01-08 12:47             ` Arnaldo Carvalho de Melo
2002-01-07 18:19         ` 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
2002-01-08  1:34         ` Miles Lane
2002-01-07 23:44       ` J.A. Magallon [this message]
2002-01-08  2:01         ` [s-h] " Alan Cox
2002-01-08  5:12           ` Linus Torvalds

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=20020108004416.A23665@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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