From: Peter Meerwald <pmeerw@pmeerw.net>
To: linux-iio@vger.kernel.org
Cc: Peter Meerwald <pmeerw@pmeerw.net>
Subject: [PATCH 3/6] iio: iio/machine.h typo
Date: Fri, 15 Jun 2012 00:50:57 +0200 [thread overview]
Message-ID: <1339714260-8361-3-git-send-email-pmeerw@pmeerw.net> (raw)
In-Reply-To: <1339714260-8361-1-git-send-email-pmeerw@pmeerw.net>
Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
---
include/linux/iio/machine.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/iio/machine.h b/include/linux/iio/machine.h
index 0b1f19b..400a453 100644
--- a/include/linux/iio/machine.h
+++ b/include/linux/iio/machine.h
@@ -14,7 +14,7 @@
* This is matched against the datasheet_name element
* of struct iio_chan_spec.
* @consumer_dev_name: Name to uniquely identify the consumer device.
- * @consumer_channel: Unique name used to idenitify the channel on the
+ * @consumer_channel: Unique name used to identify the channel on the
* consumer side.
*/
struct iio_map {
--
1.7.9.5
next prev parent reply other threads:[~2012-06-14 22:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 22:50 [PATCH 1/6] iio: sysfs-bus-iio typo Peter Meerwald
2012-06-14 22:50 ` [PATCH 2/6] iio: cleanup sysfs-bus-iio-light-lm3533-als Peter Meerwald
2012-06-15 12:48 ` Jonathan Cameron
2012-06-14 22:50 ` Peter Meerwald [this message]
2012-06-15 12:46 ` [PATCH 3/6] iio: iio/machine.h typo Jonathan Cameron
2012-06-14 22:50 ` [PATCH 4/6] iio: add IIO_ALTVOLTAGE to iio_event_monitor example Peter Meerwald
2012-06-15 12:46 ` Jonathan Cameron
2012-06-14 22:50 ` [PATCH 5/6] iio staging: typos Peter Meerwald
2012-06-15 12:45 ` Jonathan Cameron
2012-06-14 22:51 ` [PATCH 6/6] iio: iio/events.h typos Peter Meerwald
2012-06-15 12:43 ` Jonathan Cameron
2012-06-15 12:48 ` [PATCH 1/6] iio: sysfs-bus-iio typo Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2012-06-15 17:25 Peter Meerwald
2012-06-15 17:25 ` [PATCH 3/6] iio: iio/machine.h typo Peter Meerwald
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=1339714260-8361-3-git-send-email-pmeerw@pmeerw.net \
--to=pmeerw@pmeerw.net \
--cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).