From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
lm-sensors <lm-sensors@lm-sensors.org>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <srostedt@redhat.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH v3 0/4] new macro: find_closest()
Date: Thu, 19 Mar 2015 15:30:16 +0100 [thread overview]
Message-ID: <1426775420-31350-1-git-send-email-bgolaszewski@baylibre.com> (raw)
This series proposes to unduplicate the code used to find the
member in an array closest to 'x'.
The first patch adds a macro implementing the algorithm in two
flavors - for arrays sorted in ascending and descending order.
Other three patches replace duplicated code with calls to one
of these macros in some hwmon drivers.
v3:
- don't add find_closest() to kernel.h - instead create a new include
for helper macros
- don't remove RANGE_TO_REG() and FREQ_TO_REG(), but replace their
contents with find_closest() expansions
- use kernel-docs to document new macros
- rename find_closest_desc() to find_closest_descending()
v2:
https://lkml.org/lkml/2015/3/10/582
v1:
https://lkml.org/lkml/2015/2/24/509
Bartosz Golaszewski (4):
util_macros.h: add find_closest() macro
hwmon: (ina2xx) replace ina226_avg_bits() with find_closest()
hwmon: (lm85) use find_closest() in x_TO_REG() functions
hwmon: (w83795) use find_closest_descending() in pwm_freq_to_reg()
drivers/hwmon/ina2xx.c | 17 +++--------------
drivers/hwmon/lm85.c | 26 ++++++++------------------
drivers/hwmon/w83795.c | 8 +++-----
include/linux/util_macros.h | 39 +++++++++++++++++++++++++++++++++++++++
4 files changed, 53 insertions(+), 37 deletions(-)
create mode 100644 include/linux/util_macros.h
--
2.1.4
next reply other threads:[~2015-03-19 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 14:30 Bartosz Golaszewski [this message]
2015-03-19 14:30 ` [PATCH v3 1/4] util_macros.h: add find_closest() macro Bartosz Golaszewski
2015-03-19 15:15 ` Joe Perches
2015-03-19 16:21 ` Bartosz Golaszewski
2015-03-19 16:03 ` Steven Rostedt
2015-03-19 16:28 ` Bartosz Golaszewski
2015-03-19 16:32 ` Steven Rostedt
2015-03-19 16:33 ` Steven Rostedt
2015-03-19 16:48 ` Bartosz Golaszewski
2015-03-19 16:36 ` Bartosz Golaszewski
2015-03-19 14:30 ` [PATCH v3 2/4] hwmon: (ina2xx) replace ina226_avg_bits() with find_closest() Bartosz Golaszewski
2015-03-19 14:30 ` [PATCH v3 3/4] hwmon: (lm85) use find_closest() in x_TO_REG() functions Bartosz Golaszewski
2015-03-19 14:30 ` [PATCH v3 4/4] hwmon: (w83795) use find_closest_descending() in pwm_freq_to_reg() Bartosz Golaszewski
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=1426775420-31350-1-git-send-email-bgolaszewski@baylibre.com \
--to=bgolaszewski@baylibre.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=srostedt@redhat.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