summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHelia Correia <helia.correia@linux.intel.com>2013-11-28 16:02:41 +0100
committerWolfram Sang <wsa@the-dreams.de>2014-01-09 23:02:46 +0100
commitce5a111a1b59eeaef4f680efc78232c2cd2f70b7 (patch)
treefb76cb69f368e5afa4589996ff7a553e60d32953
parent5915dbf42971a743f50de6c0970ce48b0109c832 (diff)
Documentation: i2c: Remove obsolete example
Documentation/i2c/fault-codes illustrates EINVAL error code as follows: "One example would be a driver trying an SMBus Block Write with block size outside the range of 1-32 bytes." However, the actual implementation of i2c subsystem truncates data length to be 32 bytes. Hence this example cannot happen anymore, and since it's obsolete, let's simply remove it from Documentation/i2c/fault-codes. Signed-off-by: Helia Correia <helia.correia@intel.com> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
-rw-r--r--Documentation/i2c/fault-codes3
1 files changed, 0 insertions, 3 deletions
diff --git a/Documentation/i2c/fault-codes b/Documentation/i2c/fault-codes
index 045765c0b9b5..47c25abb7d52 100644
--- a/Documentation/i2c/fault-codes
+++ b/Documentation/i2c/fault-codes
@@ -64,9 +64,6 @@ EINVAL
detected before any I/O operation was started. Use a more
specific fault code when you can.
- One example would be a driver trying an SMBus Block Write
- with block size outside the range of 1-32 bytes.
-
EIO
This rather vague error means something went wrong when
performing an I/O operation. Use a more specific fault