From: Phillip Kurtenbach <pkurtenbach@googlemail.com>
To: gregkh@suse.de
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Phillip Kurtenbach <pkurtenbach@gmail.com>
Subject: [PATCH] staging: iio: whitespace cleanup
Date: Sun, 26 Sep 2010 01:11:09 +0200 [thread overview]
Message-ID: <1285456269-27582-1-git-send-email-pkurtenbach@gmail.com> (raw)
Fixed whitespace coding style issues.
Signed-off-by: Phillip Kurtenbach <pkurtenbach@gmail.com>
---
drivers/staging/iio/industrialio-core.c | 2 +-
drivers/staging/iio/industrialio-ring.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/iio/industrialio-core.c b/drivers/staging/iio/industrialio-core.c
index dd4d87a..c03e1ae 100644
--- a/drivers/staging/iio/industrialio-core.c
+++ b/drivers/staging/iio/industrialio-core.c
@@ -59,7 +59,7 @@ EXPORT_SYMBOL(__iio_change_event);
* are queued. Hence a client MUST open the chrdev before the ring buffer is
* switched on.
*/
- int __iio_push_event(struct iio_event_interface *ev_int,
+int __iio_push_event(struct iio_event_interface *ev_int,
int ev_code,
s64 timestamp,
struct iio_shared_ev_pointer *
diff --git a/drivers/staging/iio/industrialio-ring.c b/drivers/staging/iio/industrialio-ring.c
index 6ab578e..972a41a 100644
--- a/drivers/staging/iio/industrialio-ring.c
+++ b/drivers/staging/iio/industrialio-ring.c
@@ -312,7 +312,7 @@ ssize_t iio_read_ring_length(struct device *dev,
}
EXPORT_SYMBOL(iio_read_ring_length);
- ssize_t iio_write_ring_length(struct device *dev,
+ssize_t iio_write_ring_length(struct device *dev,
struct device_attribute *attr,
const char *buf,
size_t len)
--
1.7.2.3
next reply other threads:[~2010-09-25 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 23:11 Phillip Kurtenbach [this message]
2010-09-26 9:44 ` [PATCH] staging: iio: whitespace cleanup Jonathan Cameron
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=1285456269-27582-1-git-send-email-pkurtenbach@gmail.com \
--to=pkurtenbach@googlemail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pkurtenbach@gmail.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