2016-10-07 11:32 GMT+02:00 Wolfram Sang <wsa@xxxxxxxxxxxxx>:
> Linus,
>
> here is the 4.9 pull request from I2C including:
>
> * centralized error messages when registering to the core
> * improved lockdep annotations to prevent false positives
> * DT support for muxes, gates, and arbitrators
> * bus speeds can now be obtained from ACPI
> * i2c-octeon got refactored and now supports ThunderX SoCs, too
> * i2c-tegra and i2c-designware got a bigger bunch of updates
> * a couple of standard driver fixes and improvements
>
> Please pull.
>
> Thanks,
>
> Wolfram
>
>
> The following changes since commit fa8410b355251fd30341662a40ac6b22d3e38468:
>
> Linux 4.8-rc3 (2016-08-21 16:14:10 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-4.9
>
> for you to fetch changes up to 662786a5429c3a992c6f884a647ee32424822358:
>
> i2c: axxia: disable clks in case of failure in probe (2016-09-24 11:26:55 +0200)
>
> ----------------------------------------------------------------
> Alexey Khoroshilov (1):
> i2c: axxia: disable clks in case of failure in probe
>
> Andy Shevchenko (2):
> i2c: core: put literals on one line in dev_*() calls
> i2c: i801: Add support for Kaby Lake PCH-H
>
> Bartosz Golaszewski (5):
> eeprom: at24: check if the chip is functional in probe()
> i2c: export i2c_adapter_depth()
> lockdep: make MAX_LOCKDEP_SUBCLASSES unconditionally visible
> i2c: add a warning to i2c_adapter_depth()
> gpio: pca953x: fix an incorrect lockdep warning
>
Hi Wolfram,
I see you didn't pick up the follow-up patch ("gpio: pca953x: add a
comment explaining the need for a lockdep subclass"). Linus acked it
in the end and I'd really prefer for it to go into 4.9, as I don't
know if I'll have time to complete the solution for the lockdep issue
in the next development cycle. Without this explanation, the random
lockdep_set_subclass() call looks out of place.
Thanks,
Bartosz
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
