public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Ulrich Niedermann <linux-kernel@n-dimensional.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Adrian Bunk <bunk@fs.tum.de>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] move rme96xx to Documentation/sound/oss/
Date: Tue, 13 Jan 2004 20:26:29 +0100	[thread overview]
Message-ID: <86d69nzm3e.fsf@n-dimensional.de> (raw)
In-Reply-To: <20040113185432.GQ9677@fs.tum.de> (Adrian Bunk's message of "Tue, 13 Jan 2004 19:54:32 +0100")

Adrian Bunk <bunk@fs.tum.de> writes:

> In 2.6, all sound documentation with the exception of the OSS rme96xx 
> documentation is under Documentation/sound/{alsa,oss}.
>
> The patch below moves the OSS rme96xx to Documentation/sound/oss/ .
>
> diffstat output:
>
>  Documentation/sound/oss/rme96xx |  767 ++++++++++++++++++++++++++++++++
>  Documentation/sound/rme96xx     |  767 --------------------------------
>  2 files changed, 767 insertions(+), 767 deletions(-)

Please also apply the following, while you're at it.

Uli

===== sound/oss/Kconfig 1.18 vs edited =====
--- 1.18/sound/oss/Kconfig	Tue Dec 30 09:45:02 2003
+++ edited/sound/oss/Kconfig	Tue Jan 13 20:23:01 2004
@@ -1147,7 +1147,7 @@
 	help
 	  Say Y or M if you have a Hammerfall or Hammerfall light
 	  multichannel card from RME. If you want to acess advanced
-	  features of the card, read Documentation/sound/rme96xx.
+	  features of the card, read Documentation/sound/oss/rme96xx.
 
 config SOUND_AD1980
 	tristate "AD1980 front/back switch plugin"

  reply	other threads:[~2004-01-13 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 18:54 [2.6 patch] move rme96xx to Documentation/sound/oss/ Adrian Bunk
2004-01-13 19:26 ` Hans Ulrich Niedermann [this message]
2004-01-13 19:52 ` Andrew Morton
2004-01-19 22:04   ` Adrian Bunk

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=86d69nzm3e.fsf@n-dimensional.de \
    --to=linux-kernel@n-dimensional.de \
    --cc=akpm@osdl.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    /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