From: Peter Huewe <peterhuewe@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: Greg KH <gregkh@suse.de>,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
Harry Wei <jiaweiwei.xiyou@gmail.com>,
Peter Huewe <peterhuewe@gmx.de>
Subject: [PATCH 06/27] staging/dt3155v4l: Fix common spelling mistakes
Date: Sat, 26 Mar 2011 02:17:55 +0100 [thread overview]
Message-ID: <1301102296-15565-7-git-send-email-peterhuewe@gmx.de> (raw)
In-Reply-To: <20110314224746.GA21100@kroah.com>
This patch fixes a very common spelling mistake in
drivers/staging/dt3155v4l.
WRONG -> RIGHT
writting -> writing
Kernel Version: staging/staging-next 20110325 (4bbba111)
Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
---
drivers/staging/dt3155v4l/dt3155v4l.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/dt3155v4l/dt3155v4l.c b/drivers/staging/dt3155v4l/dt3155v4l.c
index 15d7efe..52a0e6e 100644
--- a/drivers/staging/dt3155v4l/dt3155v4l.c
+++ b/drivers/staging/dt3155v4l/dt3155v4l.c
@@ -122,7 +122,7 @@ read_i2c_reg(void __iomem *addr, u8 index, u8 *data)
*
* returns: zero on success or error code
*
- * This function starts writting the specified (by index) register
+ * This function starts writing the specified (by index) register
* and busy waits for the process to finish.
*/
static int
@@ -155,7 +155,7 @@ write_i2c_reg(void __iomem *addr, u8 index, u8 data)
* @index: index (internal address) of register to read
* @data: data to be written
*
- * This function starts writting the specified (by index) register
+ * This function starts writing the specified (by index) register
* and then returns.
*/
static void write_i2c_reg_nowait(void __iomem *addr, u8 index, u8 data)
@@ -173,7 +173,7 @@ static void write_i2c_reg_nowait(void __iomem *addr, u8 index, u8 data)
*
* returns: zero on success or error code
*
- * This function waits reading/writting to finish.
+ * This function waits reading/writing to finish.
*/
static int wait_i2c_reg(void __iomem *addr)
{
--
1.7.3.4
next prev parent reply other threads:[~2011-03-26 1:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 13:18 [PATCH] trivial: fix " Peter Huewe
2011-01-06 14:01 ` Jesper Juhl
2011-01-06 14:14 ` Peter Hüwe
2011-01-07 10:04 ` Jiri Kosina
2011-01-07 13:38 ` Peter Hüwe
2011-03-08 22:49 ` [PATCH v2/resend] " Peter Huewe
2011-03-14 12:00 ` Jiri Kosina
2011-03-14 20:35 ` [PATCH v3] " Peter Huewe
2011-03-14 21:57 ` [PATCH] staging/trivial: Fix " Peter Huewe
2011-03-14 22:03 ` Greg KH
2011-03-14 22:43 ` Peter Hüwe
2011-03-14 22:47 ` Greg KH
2011-03-26 1:17 ` [PATCH 0/27] " Peter Huewe
2011-03-26 1:17 ` [PATCH 01/27] staging/ath6kl: " Peter Huewe
2011-03-26 1:17 ` [PATCH 02/27] staging/bcm: " Peter Huewe
2011-03-26 1:17 ` [PATCH 03/27] staging/brcm80211: " Peter Huewe
2011-03-26 1:17 ` [PATCH 04/27] staging/comedi: " Peter Huewe
2011-03-26 1:17 ` [PATCH 05/27] staging/crystalhd: " Peter Huewe
2011-03-26 1:17 ` Peter Huewe [this message]
2011-03-26 1:17 ` [PATCH 07/27] staging/easycap: " Peter Huewe
2011-03-15 3:14 ` [PATCH] staging/trivial: " Harry Wei
2011-03-26 1:39 ` Peter Hüwe
2011-03-26 2:21 ` Harry Wei
2011-03-15 2:58 ` [PATCH v2/resend] trivial: fix " Harry Wei
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=1301102296-15565-7-git-send-email-peterhuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jiaweiwei.xiyou@gmail.com \
--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
all inboxes | Powered by JetHome®