From: I Viswanath <viswanathiyyappan@gmail.com>
To: wsa+renesas@sang-engineering.com
Cc: linux-i2c@vger.kernel.org, viswanathiyyappan@gmail.com
Subject: [PATCH v3] i2c: Fix grammatical errors in i2c_msg documentation
Date: Wed, 9 Jul 2025 21:06:44 +0530 [thread overview]
Message-ID: <20250709153644.10778-1-viswanathiyyappan@gmail.com> (raw)
Fix the following grammatical errors in i2c_msg documentation:
1. Makes only sense in → Makes sense only in
2. may have changed those standard protocol behaviors →
may alter the standard protocol behavior
Signed-off-by: I Viswanath <viswanathiyyappan@gmail.com>
---
include/uapi/linux/i2c.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/i2c.h b/include/uapi/linux/i2c.h
index 92326ebde350..aa751389de07 100644
--- a/include/uapi/linux/i2c.h
+++ b/include/uapi/linux/i2c.h
@@ -24,7 +24,7 @@
* %I2C_M_RD: read data (from slave to master). Guaranteed to be 0x0001!
*
* Optional:
- * %I2C_M_DMA_SAFE: the buffer of this message is DMA safe. Makes only sense
+ * %I2C_M_DMA_SAFE: the buffer of this message is DMA safe. Makes sense only
* in kernelspace, because userspace buffers are copied anyway
*
* Only if I2C_FUNC_10BIT_ADDR is set:
@@ -66,7 +66,7 @@
* @i2c_msg transaction segment, beginning with a (repeated) START.
*
* Alternatively, when the adapter supports %I2C_FUNC_PROTOCOL_MANGLING then
- * passing certain @flags may have changed those standard protocol behaviors.
+ * passing certain @flags may alter the standard protocol behavior.
* Those flags are only for use with broken/nonconforming slaves, and with
* adapters which are known to support the specific mangling options they need.
*/
--
2.49.0
next reply other threads:[~2025-07-09 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 15:36 I Viswanath [this message]
2025-07-14 7:19 ` [PATCH v3] i2c: Fix grammatical errors in i2c_msg documentation 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=20250709153644.10778-1-viswanathiyyappan@gmail.com \
--to=viswanathiyyappan@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).