From: Hartmut Knaack <knaack.h@gmx.de>
To: linux-iio@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Roberta Dobrescu <roberta.dobrescu@gmail.com>,
Daniel Baluta <daniel.baluta@intel.com>,
Irina Tirdea <irina.tirdea@intel.com>
Subject: [PATCH v2 0/3] iio-tools out-of-staging cleanup
Date: Wed, 10 Jun 2015 21:51:18 +0200 [thread overview]
Message-ID: <cover.1433721755.git.knaack.h@gmx.de> (raw)
Now that the iio-tools got moved out of staging, it is about time to
improve code quality to common kernel level.
Changes in V2:
iio_event_monitor: change error handling in case of read-problems
to abort the read loop, rather than just trying
again.
Hartmut Knaack (3):
tools:iio:iio_event_monitor: check if event is fully read
tools:iio: adjust coding style
tools:iio: rename variables
tools/iio/generic_buffer.c | 46 +++++++++-------
tools/iio/iio_event_monitor.c | 19 +++++--
tools/iio/iio_utils.c | 121 +++++++++++++++++++++++++-----------------
tools/iio/iio_utils.h | 15 +++---
tools/iio/lsiio.c | 43 ++++++++-------
5 files changed, 143 insertions(+), 101 deletions(-)
--
2.3.6
next reply other threads:[~2015-06-10 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 19:51 Hartmut Knaack [this message]
2015-06-10 19:51 ` [PATCH v2 1/3] tools:iio:iio_event_monitor: check if event is fully read Hartmut Knaack
2015-06-10 20:16 ` Daniel Baluta
2015-06-13 8:36 ` Hartmut Knaack
2015-06-13 8:46 ` Daniel Baluta
2015-06-13 10:00 ` Hartmut Knaack
2015-06-13 11:11 ` Cristina Georgiana Opriceana
2015-06-21 15:21 ` Jonathan Cameron
2015-06-10 19:51 ` [PATCH v2 2/3] tools:iio: adjust coding style Hartmut Knaack
2015-06-13 17:53 ` Jonathan Cameron
2015-06-10 19:51 ` [PATCH v2 3/3] tools:iio: rename variables Hartmut Knaack
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=cover.1433721755.git.knaack.h@gmx.de \
--to=knaack.h@gmx.de \
--cc=daniel.baluta@intel.com \
--cc=irina.tirdea@intel.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=roberta.dobrescu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.