From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: 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: ALSA patch for 2.5.2pre9 kernel
Date: Mon, 7 Jan 2002 16:10:38 -0200 [thread overview]
Message-ID: <20020107181038.GB1026@conectiva.com.br> (raw)
In-Reply-To: <E16Ndc4-0001sW-00@the-village.bc.nu> <Pine.LNX.4.33.0201070959430.6559-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0201070959430.6559-100000@penguin.transmeta.com>
Em Mon, Jan 07, 2002 at 10:00:57AM -0800, Linus Torvalds escreveu:
>
> On Mon, 7 Jan 2002, Alan Cox wrote:
> > > Or we could just have a really _deep_ hierarchy, and put everything under
> > > "linux/drivers/sound/..", but I'd rather break cleanly with the old.
> >
> > Christoph has an interesting point. Networking is
> >
> > net/[protocol]/
> > drivers/net/[driver]
> >
> > so by that logic we'd have
> >
> > sound/soundcore.c
> > sound/alsa/alsalibcode
> > sound/oss/osscore
> >
> > sound/drivers/cardfoo.c
> >
> > which would also be much cleaner since the supporting crap would be seperate
> > from the card drivers
>
> I would certainly not oppose that. Look sane to me, although the question
> then ends up being about "drivers/sound" or "sound/drivers" (the latter
> has the advantage that it keeps sound together, the former is more
> analogous to the "net" situation).
One ring^Wlayout to rule them all <stops here ;)> I would not be unhappy if
drivers/net became net/drivers, etc 8)
- Arnaldo
next prev parent reply other threads:[~2002-01-07 18:12 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 [this message]
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
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=20020107181038.GB1026@conectiva.com.br \
--to=acme@conectiva.com.br \
--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