From: Christoph Hellwig <hch@caldera.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: 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 18:06:56 +0100 [thread overview]
Message-ID: <20020107180656.A16283@caldera.de> (raw)
In-Reply-To: <200201071432.g07EWI802933@ns.caldera.de> <Pine.LNX.4.33.0201070858150.6450-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0201070858150.6450-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Mon, Jan 07, 2002 at 09:02:39AM -0800
On Mon, Jan 07, 2002 at 09:02:39AM -0800, Linus Torvalds wrote:
> > linux/sound is silly. It's drivers so put it under linux/drivers/sound.
>
> That was my initial reaction too, but Jaroslav clearly wants a
> higher-level generic hierarchy. Which means that we're not talking about
> _drivers_ any more, we're talking about something that is much more
> closely related to a "networking" kind of thing.
If you look at the code it clearly is driver code.
> So we could have a net-based setup, where there would be a totally
> separate "linux/sound" and "linux/drivers/sound". Which doesn't seem to
> make much sense either.
If really wants that I'd go for this.
> Or we could just have a really _deep_ hierarchy, and put everything under
> "linux/drivers/sound/..",
Yes. From a maintaince view that is no different from the same
hierarchy under linux/sound, but introducing drivers (_lots_ of drivers)
outside linux/drivers is very stupid.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2002-01-07 17:07 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 [this message]
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
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=20020107180656.A16283@caldera.de \
--to=hch@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 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.