public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aurélien Francillon" <aurel@naurel.org>
To: "Aurélien Francillon" <aurel@naurel.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-mm1
Date: Fri, 04 Mar 2005 15:19:09 +0100	[thread overview]
Message-ID: <42286E5D.9040509@naurel.org> (raw)
In-Reply-To: <422869BA.3030802@naurel.org>


[-- Attachment #1.1: Type: text/plain, Size: 406 bytes --]

Aurélien Francillon wrote:
> Andrew Morton wrote:
> 
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm1/ 
>>
>>
>>
> 

(updated patch )
By the way is there something like the Trivial Patch Monkey for mm kernel ?
thanks
Aurel

trivial patch for fscache menuconfig help documentation path and typo

Signed-off-by: Aurélien Francillon <aurel@naurel.org>




[-- Attachment #1.2: fscache-menuconfig-help-fix-documentation-path.patch --]
[-- Type: text/plain, Size: 967 bytes --]

--- 2.6.11-mm1-orig/fs/Kconfig	2005-03-04 15:12:41.000000000 +0100
+++ 2.6.11-mm1/fs/Kconfig	2005-03-04 15:08:13.000000000 +0100
@@ -442,10 +442,10 @@
 	help
 	  This option enables a generic filesystem caching manager that can be
 	  used by various network and other filesystems to cache data
-	  locally. Diffent sorts of caches can be plugged in, depending on the
+	  locally. Different sorts of caches can be plugged in, depending on the
 	  resources available.
 
-	  See Documentation/filesystems/fscache.txt for more information.
+	  See Documentation/filesystems/caching/fscache.txt for more information.
 
 config CACHEFS
 	tristate "Filesystem caching filesystem"
@@ -464,7 +464,7 @@
 	  The cache can be journalled so that the cache contents aren't
 	  destroyed in the event of a power failure.
 
-	  See Documentation/filesystems/cachefs.txt for more information.
+	  See Documentation/filesystems/caching/cachefs.txt for more information.
 
 endmenu
 

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-03-04 14:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 11:32 2.6.11-mm1 Andrew Morton
2005-03-04 13:59 ` 2.6.11-mm1 Aurélien Francillon
2005-03-04 14:19   ` Aurélien Francillon [this message]
2005-03-04 16:44 ` 2.6.11-mm1 (compile stats) John Cherry
2005-03-04 22:16 ` 2.6.11-mm1 Alexander Nyberg
2005-03-04 22:39   ` 2.6.11-mm1 Andrew Morton
2005-03-04 22:55     ` 2.6.11-mm1 Alexander Nyberg
2005-03-08 21:31       ` 2.6.11-mm1 Alexander Nyberg
2005-03-07  8:41 ` 2.6.11-mm1 Borislav Petkov
2005-03-07 21:52   ` 2.6.11-mm1: sound <-> GAMEPORT problems Adrian Bunk
2005-03-07 22:05     ` Dmitry Torokhov
2005-03-07 22:12     ` Dmitry Torokhov
2005-03-07 23:06       ` [2.6 patch] sound/pci/cs4281.c fix typos in the SUPPORT_JOYSTICK=n case Adrian Bunk
2005-03-08 10:24         ` Vojtech Pavlik
2005-03-09 11:32         ` [2.6 patch] OSS gameport fixes Adrian Bunk
2005-03-10 15:36           ` Dmitry Torokhov
2005-03-10 15:57             ` Vojtech Pavlik
2005-03-07  8:51 ` 2.6.11-mm1 Guillaume Thouvenin
2005-03-07  8:58   ` 2.6.11-mm1 Andrew Morton
2005-03-07 23:45     ` 2.6.11-mm1 Greg KH
2005-03-07 23:07 ` [-mm patch] sound/oss/soundcard.c: remove an unused variable Adrian Bunk
2005-03-08  2:33   ` Jesper Juhl
2005-03-10 17:21 ` 2.6.11-mm1 Tom Rini

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=42286E5D.9040509@naurel.org \
    --to=aurel@naurel.org \
    --cc=akpm@osdl.org \
    --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