From: Roman Fietze 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-Tag: upstream/snapshot3+hdmi~14787^2~1 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=4c44f309cd396c18b096d31f03126824c685dbe2;p=platform%2Fadaptation%2Frenesas_rcar%2Frenesas_kernel.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 Signed-off-by: Jeff Garzik --- diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index e2202e9..839b21b 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