From: Peter Meerwald <pmeerw@pmeerw.net>
To: linux-iio@vger.kernel.org
Subject: [PATCH v4 00/11] hmc5843 cleanup
Date: Thu, 17 Oct 2013 00:19:03 +0200 [thread overview]
Message-ID: <1381961954-25596-1-git-send-email-pmeerw@pmeerw.net> (raw)
v4 is addressing comments by Lars-Peter Clausen (use __be16 instead of s16) and
Jonathan Cameron (naming of _get_scale_index() vs _check_scale())
Jonathan's comment led to changes in patch 1 mainly
patch 2 is new and renames _check_samp_freq() to get_samp_freq_index() in the
same spirit and merges/inlines unused helper functions
Lars-Peter's comment is addressed in patches 3 and 4
Peter Meerwald (11):
staging:iio:hmc5843: Use SCALE instead of magn_range
staging:iio:hmc5843: Rename _check_samp_freq to get_samp_freq_index
staging:iio:hmc5843: Always read all channels values otherwise no
updates
staging:iio:hmc5843: Add trigger handling
staging:iio:hmc5843: Remove ability to change operating mode
staging:iio:hmc5843: Rename _configure() to _set_mode()
staging:iio:hmc5843: Reorganize _set_meas_conf()
staging:iio:hmc5843: Rename _set_rate() to _set_samp_freq()
staging:iio:hmc5843: Introduce _set_range_gain()
staging:iio:hmc5843: Check initialization and chip identifier
staging:iio:hmc5843: Trivial cleanup
drivers/staging/iio/magnetometer/hmc5843.c | 516 ++++++++++++++---------------
1 file changed, 240 insertions(+), 276 deletions(-)
--
1.8.4
next reply other threads:[~2013-10-16 22:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 22:19 Peter Meerwald [this message]
2013-10-16 22:19 ` [PATCH v4 01/11] staging:iio:hmc5843: Use SCALE instead of magn_range Peter Meerwald
2013-10-17 22:46 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 02/11] staging:iio:hmc5843: Rename _check_samp_freq to get_samp_freq_index Peter Meerwald
2013-10-17 22:47 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 03/11] staging:iio:hmc5843: Always read all channels values otherwise no updates Peter Meerwald
2013-10-17 22:49 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 04/11] staging:iio:hmc5843: Add trigger handling Peter Meerwald
2013-10-17 22:49 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 05/11] staging:iio:hmc5843: Remove ability to change operating mode Peter Meerwald
2013-10-17 22:50 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 06/11] staging:iio:hmc5843: Rename _configure() to _set_mode() Peter Meerwald
2013-10-17 22:50 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 07/11] staging:iio:hmc5843: Reorganize _set_meas_conf() Peter Meerwald
2013-10-17 22:51 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 08/11] staging:iio:hmc5843: Rename _set_rate() to _set_samp_freq() Peter Meerwald
2013-10-17 22:52 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 09/11] staging:iio:hmc5843: Introduce _set_range_gain() Peter Meerwald
2013-10-17 22:52 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 10/11] staging:iio:hmc5843: Check initialization and chip identifier Peter Meerwald
2013-10-17 22:52 ` Jonathan Cameron
2013-10-16 22:19 ` [PATCH v4 11/11] staging:iio:hmc5843: Trivial cleanup Peter Meerwald
2013-10-17 22:53 ` 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=1381961954-25596-1-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).