From: Helia Correia <helia.correia-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jerome.blin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, "Correia,
Helia" <helia.correia-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: [PATCH] Documentation: i2c: Remove obsolete example
Date: Thu, 28 Nov 2013 16:02:41 +0100 [thread overview]
Message-ID: <52975B11.2090006@linux.intel.com> (raw)
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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
---
Documentation/i2c/fault-codes | 3 ---
1 file changed, 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
--
1.8.1.2
next reply other threads:[~2013-11-28 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 15:02 Helia Correia [this message]
[not found] ` <52975B11.2090006-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2014-01-09 22:00 ` [PATCH] Documentation: i2c: Remove obsolete example Wolfram Sang
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=52975B11.2090006@linux.intel.com \
--to=helia.correia-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=helia.correia-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=jerome.blin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.