From: Miles Lane <miles@megapathdsl.net>
To: Christoph Hellwig <hch@ns.caldera.de>
Cc: Abramo Bagnara <abramo@alsa-project.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jaroslav Kysela <perex@suse.cz>,
sound-hackers@zabbo.net, linux-sound@vger.rutgers.edu,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [s-h] Re: ALSA patch for 2.5.2pre9 kernel
Date: 07 Jan 2002 18:53:03 -0800 [thread overview]
Message-ID: <1010458384.27296.28.camel@stomata.megapathdsl.net> (raw)
In-Reply-To: <200201072125.g07LPgE02318@ns.caldera.de>
In-Reply-To: <200201072125.g07LPgE02318@ns.caldera.de>
On Mon, 2002-01-07 at 13:25, Christoph Hellwig wrote:
> In article <3C39E6A0.34A88990@alsa-project.org> you wrote:
> > If you want to keep top level cleaner and avoid proliferation of entries
> > we might have:
> >
> > subsys/sound
> > subsys/sound/drivers
> > subsys/net
> > subsys/net/drivers
>
> And what part of the kernel is no subsystem?
> Your subsystem directory is superflous.
Change subsys/ to some name that means "not device-specific".
The point is that the net and sound system-level stuff isn't
composed of device-specific drivers and the other directories
below linux/ do not have a bunch of device-specific drivers
associated with them (kernel, fs and mm).
> If, for some reason, we want to move all code in the kernel around
> we should do it once and in a planned manner.
Maybe a better structure is needed, but moving /net alone
would be a big project.
Miles
next prev parent reply other threads:[~2002-01-08 2:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 17:39 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-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 [this message]
2002-01-07 18:38 ` Sebastian Dröge
2002-01-07 21:32 ` Thierry Vignaud
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
2002-01-07 19:03 Dimitrie Paun
2002-01-07 20:51 Steven Walter
[not found] <20020108102833.A2927@werewolf.able.es>
2002-01-08 9:30 ` J.A. Magallon
2002-01-08 9:52 ` Abramo Bagnara
2002-01-08 10:12 ` Takashi Iwai
2002-01-08 10:18 ` Jaroslav Kysela
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-08 10:34 ` Takashi Iwai
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=1010458384.27296.28.camel@stomata.megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=abramo@alsa-project.org \
--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
all inboxes | Powered by JetHome®