Fix two typos in the i2c documentation.
Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
Documentation/i2c/functionality | 2 +-
Documentation/i2c/writing-clients | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- linux-2.4.31.orig/Documentation/i2c/functionality 2000-12-29
23:35:47.000000000 +0100
+++ linux-2.4.31/Documentation/i2c/functionality 2005-07-28
19:06:36.000000000 +0200
@@ -115,7 +115,7 @@
If you try to access an adapter from a userspace program, you will have
to use the /dev interface. You will still have to check whether the
functionality you need is supported, of course. This is done using
-the I2C_FUNCS ioctl. An example, adapted from the lm_sensors i2c_detect
+the I2C_FUNCS ioctl. An example, adapted from the lm_sensors i2cdetect
program, is below:
int file;
--- linux-2.4.31.orig/Documentation/i2c/writing-clients 2005-04-09
12:14:20.000000000 +0200
+++ linux-2.4.31/Documentation/i2c/writing-clients 2005-07-29
19:32:57.000000000 +0200
@@ -302,7 +302,7 @@
These are automatically translated to insmod variables of the form
force_foo.
-So we have a generic insmod variabled `force', and chip-specific variables
+So we have a generic insmod variable `force', and chip-specific variables
`force_CHIPNAME'.
Fortunately, as a module writer, you just have to define the `normal'
--
Jean Delvare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
