diff options
author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-05-25 10:56:30 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-05-25 10:56:30 -0700 |
commit | 588079342e2cf29fd1c33b567366519b11d83ab8 (patch) | |
tree | 035d118d3ca1b65babf7d2343f80e6bb9d4d12c4 /scripts/recordmcount.c | |
parent | c4a6ca97439a40164cd65e7f695a9f380776817f (diff) | |
parent | 34683a5c6e0ffaa61528ff71c283efe3063cc53f (diff) |
Merge tag 'iio-for-3.16c' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next
Jonathan writes:
Third round of new stuff for IIO in the 3.16 cycle.
This (rather late) set consists only of fixes to patches earlier in the
cycle or minor fixes for other problems (such as randconfig build issues
picked up by Arnd). I've included the general minor fixes here as it is
very late in the current cycle and they can all wait for the merge window.
* Recent change to hid-sensors introduced a possible infinite loop due to a
typo. In the same series, a report interval unit read was added but in the
case where the hardware doesn't support it a value of 0 would lead to some
nasty issues. The patch sets it to the specified default of msecs.
* Anon inodes were used by IIO without being explicitly selected. This has
been true for a long time so it clearly only effects rather unusual
configurations (rand configs)
* at91 requires the input subsytem but this wasn't explicity in the Kconfig.
* A couple of parts supported by the max1363 driver were using the wrong
iio_chan_spec arrays and hence would missreport their bit depths. This has
been there a long time and was never right so isn't a regression.
Diffstat (limited to 'scripts/recordmcount.c')
0 files changed, 0 insertions, 0 deletions