From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
torvalds@osdl.org, akpm@osdl.org
Subject: Re: [PATCH] Update devices.txt
Date: Sun, 23 Apr 2006 19:05:51 +0100 [thread overview]
Message-ID: <20060423180551.GB3270@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0604231622120.5207@yvahk01.tjqt.qr>
On Sun, Apr 23, 2006 at 04:25:19PM +0200, Jan Engelhardt wrote:
> @@ -262,13 +261,13 @@
> NOTE: These devices permit both read and write access.
>
> 7 block Loopback devices
> - 0 = /dev/loop0 First loopback device
> - 1 = /dev/loop1 Second loopback device
> + 0 = /dev/loop0 First loop device
> + 1 = /dev/loop1 Second loop device
> ...
>
> - The loopback devices are used to mount filesystems not
> + The loop devices are used to mount filesystems not
> associated with block devices. The binding to the
> - loopback devices is handled by mount(8) or losetup(8).
> + loop devices is handled by mount(8) or losetup(8).
This seems to rename "loopback" to "loop", but leaves the heading
"Loopback devices" using the "loopback" term. Maybe it should be
"Loop devices" ?
> @@ -1737,7 +1736,7 @@
> 0 = /dev/ubda First user-mode block device
> 16 = /dev/udbb Second user-mode block device
> ...
> -
> +
This introduces white space at the end of the line. Please remove.
> Partitions are handled in the same way as for IDE
> disks (see major number 3) except that the limit on
> partitions is 15.
> @@ -2311,7 +2310,7 @@
> 0 = /dev/drbd0 First DRBD device
> 1 = /dev/drbd1 Second DRBD device
> ...
> -
> +
This introduces white space at the end of the line. Please remove.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2006-04-23 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 14:25 Jan Engelhardt
2006-04-23 18:05 ` Russell King [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=20060423180551.GB3270@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=jengelh@linux01.gwdg.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
all inboxes | Powered by JetHome®