From: Shailendra Verma <shailendra.capricorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Shailendra Verma
<shailendra.capricorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 11/11] i2c-core: Fix typo in comment
Date: Mon, 18 May 2015 22:24:01 +0530 [thread overview]
Message-ID: <1431968041-3226-1-git-send-email-shailendra.capricorn@gmail.com> (raw)
Signed-off-by: Shailendra Verma <shailendra.capricorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
drivers/i2c/i2c-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
index 987c124..c40141b 100644
--- a/drivers/i2c/i2c-core.c
+++ b/drivers/i2c/i2c-core.c
@@ -1673,7 +1673,7 @@ void i2c_del_adapter(struct i2c_adapter *adap)
* FIXME: This is old code and should ideally be replaced by an
* alternative which results in decoupling the lifetime of the struct
* device from the i2c_adapter, like spi or netdev do. Any solution
- * should be throughly tested with DEBUG_KOBJECT_RELEASE enabled!
+ * should be thoroughly tested with DEBUG_KOBJECT_RELEASE enabled!
*/
init_completion(&adap->dev_released);
device_unregister(&adap->dev);
--
1.7.9.5
next reply other threads:[~2015-05-18 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 16:54 Shailendra Verma [this message]
[not found] ` <1431968041-3226-1-git-send-email-shailendra.capricorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-19 4:48 ` [PATCH 11/11] i2c-core: Fix typo in comment Sudip Mukherjee
[not found] ` <CA+tKcn8exGWjb5Ttr9fMtKhSA_NKf2umZs5JDtC+uTfLKc9fAA@mail.gmail.com>
[not found] ` <CA+tKcn8exGWjb5Ttr9fMtKhSA_NKf2umZs5JDtC+uTfLKc9fAA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-19 5:55 ` Sudip Mukherjee
2015-05-19 6:20 ` Wolfram Sang
[not found] ` <20150519062046.GB4448-oo5tB6JMkjKRinMKxDlMNPwbnWRJjS81@public.gmane.org>
2015-05-19 6:50 ` Sudip Mukherjee
2015-05-31 23:43 ` 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=1431968041-3226-1-git-send-email-shailendra.capricorn@gmail.com \
--to=shailendra.capricorn-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-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 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).