From: Crestez Dan Leonard <leonard.crestez@intel.com>
To: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Daniel Baluta <daniel.baluta@intel.com>,
Crestez Dan Leonard <leonard.crestez@intel.com>
Subject: [PATCH v4 0/3] iio: generic_buffer: Select device/trigger by number
Date: Mon, 30 May 2016 18:19:25 +0300 [thread overview]
Message-ID: <cover.1464610998.git.leonard.crestez@intel.com> (raw)
This patch series adds support for selecting iio devices/triggers by numeric id
rather than just name. This is useful because the names are not actually
guaranteed to be unique.
Changes since v3:
* Rebase on top of latest jic23/testing
* Fix handling of --trigger-num 0. Initialize trig_num to -1 and check if >= 0
for valid id.
Jonathan: you replied to v3 saying that they were applied but I don't see those
patches on any branch from your repo:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
Crestez Dan Leonard (3):
iio: generic_buffer: Cleanup when receiving signals
iio: generic_buffer: Add --device-num option
iio: generic_buffer: Add --trigger-num option
tools/iio/iio_generic_buffer.c | 261 ++++++++++++++++++++++++++++-------------
1 file changed, 181 insertions(+), 80 deletions(-)
--
2.5.5
next reply other threads:[~2016-05-30 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 15:19 Crestez Dan Leonard [this message]
2016-05-30 15:19 ` [PATCH v4 1/3] iio: generic_buffer: Cleanup when receiving signals Crestez Dan Leonard
2016-05-30 15:19 ` [PATCH v4 2/3] iio: generic_buffer: Add --device-num option Crestez Dan Leonard
2016-05-30 15:19 ` [PATCH v4 3/3] iio: generic_buffer: Add --trigger-num option Crestez Dan Leonard
2016-06-03 18:54 ` [PATCH v4 0/3] iio: generic_buffer: Select device/trigger by number Crestez Dan Leonard
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.1464610998.git.leonard.crestez@intel.com \
--to=leonard.crestez@intel.com \
--cc=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).