From: <gregkh@linuxfoundation.org>
To: mranostay@gmail.com, gregkh@linuxfoundation.org, jic23@kernel.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "iio: proximity: as3935: remove triggered buffer processing" has been added to the 4.4-stable tree
Date: Sun, 24 Jul 2016 17:30:29 -0700 [thread overview]
Message-ID: <1469406629232110@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
iio: proximity: as3935: remove triggered buffer processing
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
iio-proximity-as3935-remove-triggered-buffer-processing.patch
and it can be found in the queue-4.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From 7d0643634ea567969bf3f3ed6193a9d6fc75653b Mon Sep 17 00:00:00 2001
From: Matt Ranostay <mranostay@gmail.com>
Date: Sat, 21 May 2016 20:01:02 -0700
Subject: iio: proximity: as3935: remove triggered buffer processing
From: Matt Ranostay <mranostay@gmail.com>
commit 7d0643634ea567969bf3f3ed6193a9d6fc75653b upstream.
Triggered buffers shouldn't return processed data, and the respective
conversion was overflowing the defined .realbits for the channel.
Cc: george.mccollister@gmail.com
Signed-off-by: Matt Ranostay <mranostay@gmail.com>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/iio/proximity/as3935.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/iio/proximity/as3935.c
+++ b/drivers/iio/proximity/as3935.c
@@ -213,7 +213,6 @@ static irqreturn_t as3935_trigger_handle
if (ret)
goto err_read;
val &= AS3935_DATA_MASK;
- val *= 1000;
iio_push_to_buffers_with_timestamp(indio_dev, &val, pf->timestamp);
err_read:
Patches currently in stable-queue which might be from mranostay@gmail.com are
queue-4.4/iio-hudmidity-hdc100x-fix-incorrect-shifting-and-scaling.patch
queue-4.4/iio-proximity-as3935-fix-buffer-stack-trashing.patch
queue-4.4/iio-light-apds9960-add-the-missing-dev.parent.patch
queue-4.4/iio-proximity-as3935-correct-iio_chan_info_raw-output.patch
queue-4.4/iio-proximity-as3935-remove-triggered-buffer-processing.patch
queue-4.4/iio-humidity-hdc100x-correct-humidity-integration-time-mask.patch
queue-4.4/iio-humidity-hdc100x-fix-iio_temp-channel-reporting.patch
reply other threads:[~2016-07-25 0:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1469406629232110@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=mranostay@gmail.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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 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.