From: Vladimirs Ambrosovs <rodriguez.twister@gmail.com>
To: sudipm.mukherjee@gmail.com, jic23@kernel.org,
daniel.baluta@intel.com, dan.carpenter@oracle.com,
gregkh@linuxfoundation.org
Cc: cristina.opriceana@gmail.com,
driverdev-devel@linuxdriverproject.org,
linux-iio@vger.kernel.org
Subject: [PATCH v3 0/3] staging: iio_simple_dummy: minor driver fixes
Date: Sat, 30 May 2015 11:20:14 +0300 [thread overview]
Message-ID: <1432974017-24547-1-git-send-email-rodriguez.twister@gmail.com> (raw)
v3 Fixed the function prototypes in header file, and the dummy inline
function return type, which cause the build break when
CONFIG_IIO_SIMPLE_DUMMY_EVENTS and CONFIG_IIO_SIMPLE_DUMMY_BUFFER
are enabled.
v2 Fixed the code as per the comments from version 1:
* Removed unnecessary comments
* Fixed the label name to address label location
* Changed the type of functions, which always return 0 to void
Vladimirs Ambrosovs (3):
staging: iio_simple_dummy: fix init function
staging: iio_simple_dummy: fix return types
staging: iio_simple_dummy: fix module_param type
drivers/staging/iio/iio_dummy_evgen.c | 4 +---
drivers/staging/iio/iio_simple_dummy.c | 21 +++++++++++----------
drivers/staging/iio/iio_simple_dummy_events.c | 4 +---
3 files changed, 13 insertions(+), 16 deletions(-)
--
2.4.1
next reply other threads:[~2015-05-30 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 8:20 Vladimirs Ambrosovs [this message]
2015-05-30 8:20 ` [PATCH v3 1/3] staging: iio_simple_dummy: fix init function Vladimirs Ambrosovs
2015-06-01 10:21 ` Jonathan Cameron
2015-05-30 8:20 ` [PATCH v3 2/3] staging: iio_simple_dummy: fix return types Vladimirs Ambrosovs
2015-06-01 10:21 ` Jonathan Cameron
2015-05-30 8:20 ` [PATCH v3 3/3] staging: iio_simple_dummy: fix module_param type Vladimirs Ambrosovs
2015-06-01 10:23 ` 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=1432974017-24547-1-git-send-email-rodriguez.twister@gmail.com \
--to=rodriguez.twister@gmail.com \
--cc=cristina.opriceana@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel.baluta@intel.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).