linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org,
	Hans Ulrich Niedermann <linux-kernel@n-dimensional.de>
Subject: Re: [2.6 patch] move rme96xx to Documentation/sound/oss/
Date: Mon, 19 Jan 2004 23:04:13 +0100	[thread overview]
Message-ID: <20040119220413.GS12027@fs.tum.de> (raw)
In-Reply-To: <20040113115240.6aec2dea.akpm@osdl.org>

On Tue, Jan 13, 2004 at 11:52:40AM -0800, Andrew Morton wrote:
> Adrian Bunk <bunk@fs.tum.de> wrote:
> >
> > The patch below moves the OSS rme96xx to Documentation/sound/oss/ .
> 
> It would be better to do this with a bk rename.  Please remind us when Linus
> returns.

Hi Linus,

in 2.6, all sound documentation with the exception of the OSS rme96xx 
documentation is under Documentation/sound/{alsa,oss}.

Please do the BK equivalent of a
  mv Documentation/sound/rme96xx \
     Documentation/sound/oss/

and apply the patch by Hans Ulrich Niedermann below.

TIA
Adrian

--- 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-19 22:04 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
2004-01-13 19:52 ` Andrew Morton
2004-01-19 22:04   ` Adrian Bunk [this message]

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=20040119220413.GS12027@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@n-dimensional.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).