From: Jonathan Cameron <jic23@kernel.org>
To: Ye Xiang <xiang.ye@intel.com>
Cc: jikos@kernel.org, srinivas.pandruvada@linux.intel.com,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] resolve read hystersis return invalid argument issue for hid sensors
Date: Sat, 6 Feb 2021 16:39:19 +0000 [thread overview]
Message-ID: <20210206163919.7993d392@archlinux> (raw)
In-Reply-To: <20210201054921.18214-1-xiang.ye@intel.com>
On Mon, 1 Feb 2021 13:49:19 +0800
Ye Xiang <xiang.ye@intel.com> wrote:
> This patch series move get sensitivity attribute to common layer and
> resolve read hystersis return invalid argument issue for hid sensors als,
> incli-3d, rotation, and press on intel ISH Platform.
Hi Ye Xiang
Series looks good to me.
Now this series touches a few bits of code outside of IIO so ideally
I'm looking for acks from:
@ Jiri for the header
@ Alessandro / Alexandre (+CC) for RTC
Both changes are trivial but might cause them some noise in other work
going on in their subsystems.
For reference:
https://lore.kernel.org/linux-iio/20210201054921.18214-2-xiang.ye@intel.com/
Thanks,
Jonathan
>
> ---
> v2:
> - separate the add relative sensitivity patch to the next patch series.
>
> Ye Xiang (2):
> iio: hid-sensors: Move get sensitivity attribute to hid-sensor-common
> hid-sensors: Add more data fields for sensitivity checking
>
> drivers/iio/accel/hid-sensor-accel-3d.c | 23 ++++++-------
> .../hid-sensors/hid-sensor-attributes.c | 17 +++++++++-
> drivers/iio/gyro/hid-sensor-gyro-3d.c | 19 ++++-------
> drivers/iio/humidity/hid-sensor-humidity.c | 16 ++++------
> drivers/iio/light/hid-sensor-als.c | 20 +++++-------
> drivers/iio/light/hid-sensor-prox.c | 27 +++++-----------
> drivers/iio/magnetometer/hid-sensor-magn-3d.c | 32 ++++++-------------
> drivers/iio/orientation/hid-sensor-incl-3d.c | 20 +++++-------
> drivers/iio/orientation/hid-sensor-rotation.c | 24 ++++++--------
> .../position/hid-sensor-custom-intel-hinge.c | 20 ++++--------
> drivers/iio/pressure/hid-sensor-press.c | 20 +++++-------
> .../iio/temperature/hid-sensor-temperature.c | 16 ++++------
> drivers/rtc/rtc-hid-sensor-time.c | 4 ++-
> include/linux/hid-sensor-hub.h | 4 ++-
> 14 files changed, 111 insertions(+), 151 deletions(-)
>
next prev parent reply other threads:[~2021-02-06 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 5:49 [PATCH v2 0/2] resolve read hystersis return invalid argument issue for hid sensors Ye Xiang
2021-02-01 5:49 ` [PATCH v2 1/2] iio: hid-sensors: Move get sensitivity attribute to hid-sensor-common Ye Xiang
2021-02-06 16:55 ` Alexandre Belloni
2021-02-01 5:49 ` [PATCH v2 2/2] hid-sensors: Add more data fields for sensitivity checking Ye Xiang
2021-02-06 16:39 ` Jonathan Cameron [this message]
2021-02-18 13:17 ` [PATCH v2 0/2] resolve read hystersis return invalid argument issue for hid sensors 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=20210206163919.7993d392@archlinux \
--to=jic23@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=xiang.ye@intel.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).