From: Laszlo Papp <lpapp@kde.org>
To: broonie@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Laszlo Papp <lpapp@kde.org>
Subject: [PATCH] include/linux/regmap.h: fix a couple of typos
Date: Wed, 8 Jan 2014 17:22:18 +0000 [thread overview]
Message-ID: <1389201738-31406-1-git-send-email-lpapp@kde.org> (raw)
These sentences are not proper English due to the typos. I had initially caught
one of them while trying to understand the regmap feature, and then I just ran
the vim spell checker, and went through all the items that would need to be
fixed for this header file.
Signed-off-by: Laszlo Papp <lpapp@kde.org>
---
include/linux/regmap.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/include/linux/regmap.h b/include/linux/regmap.h
index e559078..6305657 100644
--- a/include/linux/regmap.h
+++ b/include/linux/regmap.h
@@ -122,9 +122,9 @@ typedef void (*regmap_unlock)(void *);
* volatile_table (see below) is not, the check is performed on
* such table (a register is volatile if it belongs to one of
* the ranges specified by volatile_table).
- * @precious_reg: Optional callback returning true if the rgister
+ * @precious_reg: Optional callback returning true if the register
* should not be read outside of a call from the driver
- * (eg, a clear on read interrupt status register). If this
+ * (e.g. a clear on read interrupt status register). If this
* field is NULL but precious_table (see below) is not, the
* check is performed on such table (a register is precious if
* it belongs to one of the ranges specified by precious_table).
@@ -136,9 +136,9 @@ typedef void (*regmap_unlock)(void *);
* are not overridden).
* @reg_read: Optional callback that if filled will be used to perform
* all the reads from the registers. Should only be provided for
- * devices whos read operation cannot be represented as a simple read
- * operation on a bus such as SPI, I2C, etc. Most of the devices do
- * not need this.
+ * devices whose read operation cannot be represented as a simple
+ * read operation on a bus such as SPI, I2C, etc. Most of the
+ * devices do not need this.
* @reg_write: Same as above for writing.
* @fast_io: Register IO is fast. Use a spinlock instead of a mutex
* to perform locking. This field is ignored if custom lock/unlock
--
1.8.5.1
next reply other threads:[~2014-01-08 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 17:22 Laszlo Papp [this message]
2014-01-08 18:07 ` [PATCH] include/linux/regmap.h: fix a couple of typos Mark Brown
2014-01-08 18:59 ` Laszlo Papp
2014-01-08 19:07 ` Mark Brown
2014-01-08 21:02 ` Laszlo Papp
2014-01-08 21:08 ` Laszlo Papp
2014-01-08 21:49 ` Mark Brown
2014-01-09 1:46 ` Laszlo Papp
2014-01-09 2:43 ` Randy Dunlap
2014-01-09 10:22 ` Laszlo Papp
2014-01-09 12:23 ` Mark Brown
2014-01-09 11:18 ` Mark Brown
2014-01-08 22:04 ` Randy Dunlap
2014-01-08 19:07 ` Randy Dunlap
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=1389201738-31406-1-git-send-email-lpapp@kde.org \
--to=lpapp@kde.org \
--cc=broonie@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox