mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: perex@suse.cz (Jaroslav Kysela)
Cc: sound-hackers@zabbo.net, linux-sound@vger.rutgers.edu,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: ALSA patch for 2.5.2pre9 kernel
Date: Mon, 7 Jan 2002 15:32:18 +0100	[thread overview]
Message-ID: <200201071432.g07EWI802933@ns.caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.31.0201061814580.545-100000@pnote.perex-int.cz>

In article <Pine.LNX.4.31.0201061814580.545-100000@pnote.perex-int.cz> you wrote:
> The latest patch is alsa-2002-01-06-1-linux-2.5.2pre9.patch.gz and
> contains:

> * moved linux/drivers/sound directory to linux/sound/oss
> * moved sound core files to linux/sound
> * integrated ALSA kernel code
>   - linux/include/sound - sound header files
>   - linux/sound/core	- midlevel (no hw dependent) code
>   - linux/sound/drivers - generic drivers (no arch dependent)
>   - linux/sound/i2c     - reduced I2C core and drivers
>   - linux/sound/isa	- ISA sound hardware drivers
>   - linux/sound/pci	- PCI sound hardware drivers
>   - linux/sound/ppc	- PowerPC sound hardware drivers
>   - linux/sound/synth	- generic synthesizer support code

> We appreciate any comments regarding directory structure

linux/sound is silly.  It's drivers so put it under linux/drivers/sound.
Everything else seems to be sane to me.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

  reply	other threads:[~2002-01-07 14:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06 17:39 Jaroslav Kysela
2002-01-07 14:32 ` Christoph Hellwig [this message]
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
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

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=200201071432.g07EWI802933@ns.caldera.de \
    --to=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®