All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abramo Bagnara <abramo@alsa-project.org>
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: [s-h] Re: ALSA patch for 2.5.2pre9 kernel
Date: Mon, 07 Jan 2002 19:39:36 +0100	[thread overview]
Message-ID: <3C39EB68.BC8C804@alsa-project.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0201071024450.6671-100000@penguin.transmeta.com>

Linus Torvalds wrote:
> 
> On Mon, 7 Jan 2002, Abramo Bagnara wrote:
> >
> > IMO the latter makes much more sense (also for "net" case), but I doubt
> > you're willing to change current schema.
> 
> Agreed. I do not really think that it makes sense to move "drivers/net" to
> "net/drivers" even if it _would_ be the logical way to group all net
> things together. Whatever potential incremental advantage (if any) just
> isn't worth the disruption.
> 
> > If you want to keep top level cleaner and avoid proliferation of entries
> > we might have:
> >
> > subsys/sound
> ...
> 
> No, I hate to create structure abstractions for their own sake, and a
> "subsys" kind of abstraction doesn't really add any information.

Ok, I agree.

Just to resume, you think that the way to go is:

1) to have sound/ with *all* sound related stuff inside
2) to leave drivers/net/ and net/ like they are now (because although
it's suboptimal, to change it is a mess we don't want to face now)

Right?

-- 
Abramo Bagnara                       mailto:abramo@alsa-project.org

Opera Unica                          Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy

ALSA project               http://www.alsa-project.org
It sounds good!

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

Thread overview: 41+ 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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: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

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=3C39EB68.BC8C804@alsa-project.org \
    --to=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 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.