From: Roman Fietze <roman.fietze@telemotive.de>
Date: Wed, 21 Apr 2010 10:17:12 +0000 (+0200)
Subject: libata: fix docs, RE port and device of libata.force ID separated by point
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=4c44f309cd396c18b096d31f03126824c685dbe2;p=GitHub%2FLineageOS%2Fandroid_kernel_samsung_universal7580.git

libata: fix docs, RE port and device of libata.force ID separated by point

According to libata-core correctly around line 6572:

	/* parse id */
	p = strchr(id, '.');
	...

the optional device is separated from the port in the libata.force ID
by a point or dot instead of by a colon.

Fix documentation to reflect this.

Signed-off-by: Roman Fietze <roman.fietze@telemotive.de>
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
---

diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index e2202e93b14..839b21b0699 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -1194,7 +1194,7 @@ and is between 256 and 4096 characters. It is defined in the file
 
 	libata.force=	[LIBATA] Force configurations.  The format is comma
 			separated list of "[ID:]VAL" where ID is
-			PORT[:DEVICE].  PORT and DEVICE are decimal numbers
+			PORT[.DEVICE].  PORT and DEVICE are decimal numbers
 			matching port, link or device.  Basically, it matches
 			the ATA ID string printed on console by libata.  If
 			the whole ID part is omitted, the last PORT and DEVICE