From: Patrick Ringl <patrick_@freenet.de>
To: linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, axboe@kernel.dk
Subject: [PATCH] fix typo in drivers/block/Kconfig
Date: Sun, 25 Mar 2007 03:30:34 +0200 [thread overview]
Message-ID: <4605D0BA.2060801@freenet.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
Hello,
this is just a QA / cosmetic fix .. nevertheless the documentation about
modules / drivers should be appropriate to the great work of those who
write all the real important stuff. :-)
The following patch is against 2.6.21-rc4:
--- linux-2.6.20-o/drivers/block/Kconfig 2007-03-18 00:04:53.000000000 +0100
+++ linux-2.6.20/drivers/block/Kconfig 2007-03-25 00:57:29.000000000 +0100
@@ -383,7 +383,7 @@
default "16"
depends on BLK_DEV_RAM
help
- The default value is 16 RAM disks. Change this if you know what
+ The default value is 16 RAM disks. Change this if you know what you
are doing. If you boot from a filesystem that needs to be extracted
in memory, you will need at least one RAM disk (e.g. root on cramfs).
---
regards,
Patrick
[-- Attachment #2: drivers_block_amount-of-ram-disks_typo_fix --]
[-- Type: text/plain, Size: 507 bytes --]
--- linux-2.6.20-o/drivers/block/Kconfig 2007-03-18 00:04:53.000000000 +0100
+++ linux-2.6.20/drivers/block/Kconfig 2007-03-25 00:57:29.000000000 +0100
@@ -383,7 +383,7 @@
default "16"
depends on BLK_DEV_RAM
help
- The default value is 16 RAM disks. Change this if you know what
+ The default value is 16 RAM disks. Change this if you know what you
are doing. If you boot from a filesystem that needs to be extracted
in memory, you will need at least one RAM disk (e.g. root on cramfs).
reply other threads:[~2007-03-25 1:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4605D0BA.2060801@freenet.de \
--to=patrick_@freenet.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.