| commit | c6b0333baea0acbe792c22ac71a04e40e26a8398 | |
| author | Matt Ranostay <matt@ranostay.consulting> | |
| Tue, 17 Jan 2017 02:04:18 +0000 (16 18:04 -0800) | ||
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Thu, 9 Feb 2017 07:08:30 +0000 (9 08:08 +0100) | ||
| tree | 2796ea9f3c869ffc3a33d46f319561de46018c5c | treesnapshot (tar.gz zip) |
| parent | 12c2fcf6bcf7da2d861ab0fe36550e39dd783ff9 | commitdiff |
iio: health: max30100: fixed parenthesis around FIFO count check
commit 828f84ee8f84710ea1818b3565add268bcb824c8 upstream.
FIFO was being read every sample after the "almost full" state was
reached. This was due to an incorrect placement of the parenthesis
in the while condition check.
Note - the fixes tag is not actually correct, but the fix in this patch
would also be needed for it to function correctly so we'll go with that
one. Backports should pick up both.
Signed-off-by: Matt Ranostay <matt@ranostay.consulting>
Fixes: b74fccad7 ("iio: health: max30100: correct FIFO check condition")
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit 828f84ee8f84710ea1818b3565add268bcb824c8 upstream.
FIFO was being read every sample after the "almost full" state was
reached. This was due to an incorrect placement of the parenthesis
in the while condition check.
Note - the fixes tag is not actually correct, but the fix in this patch
would also be needed for it to function correctly so we'll go with that
one. Backports should pick up both.
Signed-off-by: Matt Ranostay <matt@ranostay.consulting>
Fixes: b74fccad7 ("iio: health: max30100: correct FIFO check condition")
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| drivers/iio/health/max30100.c | diffblobblamehistory |