summaryrefslogtreecommitdiff
path: root/include/trace
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-01-23 09:29:06 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-01-23 09:29:06 +0100
commit9579c4dc21292f375715d7acca439dac9855b3e9 (patch)
treecaf374a799c6c5f8bdf865d7fc0e936e9685f4ca /include/trace
parenta121103c922847ba5010819a3f250f1f7fc84ab8 (diff)
parent5c113b5e0082e90d2e1c7b12e96a7b8cf0623e27 (diff)
Merge tag 'iio-fixes-for-4.10b' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus
Jonathan writes: Second set of IIO fixes for the 4.10 cycle. * afe4403 - retrieve valid iio_dev in suspend / resume. Previously using the wrong dev for a call to dev_to_iio_dev. * afe4404 - retrieve valid iio_dev in suspend / resume. Previously using the wrong dev for a call to dev_to_iio_dev. * dht11 - Something seems to have caused a regression in timing on the raspberry pi 2B. However, the bug that it threw up was real. msleep was occasionally resulting in very long sleeps, over the limit possible to read from this chip. Switch to usleep_range to avoid this. The timing needed by this part is very fiddly. * max30100 - wrong parenthesis around fifo count check meant it always read after the almost_full state had been reached. I've tagged this with a fixes tag which covers the last patch that it will not need precursor patches. The bug predates that but will need backporting. * palmas_gpadc. - retrieve valid iio_dev in suspend / resume. Previously using the wrong dev for a call to dev_to_iio_dev.
Diffstat (limited to 'include/trace')
0 files changed, 0 insertions, 0 deletions
span title='2017-02-01 12:46:17 -0500'>2017-02-01Merge tag 'wireless-drivers-next-for-davem-2017-02-01' of git://git.kernel.or...David S. Miller2-1/+2 2017-02-01net: fix ndo_features_check/ndo_fix_features comment orderingDimitris Michailidis1-14/+15