On Mon, 10 Jul 2017, Javier Martinez Canillas wrote: > Hello Lee, > > On Thu, Jun 15, 2017 at 8:49 PM, Javier Martinez Canillas > <javier@xxxxxxxxxxxx> wrote: > > > > This series add OF device ID tables to mfd I2C drivers whose devices are > > either used in Device Tree source files or are listed in binding docs as > > a compatible string. > > > > That's done because the plan is to change the I2C core to report proper OF > > modaliases instead of always reporting a MODALIAS=i2c:<foo> regardless if > > a device was registered via DT or using the legacy platform data mechanism. > > > > So these patches will make sure that mfd I2C drivers modules will continue > > to be autoloaded once the I2C core is changed to report proper OF modalias. > > > > Users didn't have a vendor prefix in the used compatible strings, but since > > there wasn't a DT binding document for these drivers, it can be said that > > were working for mere luck and so this series fixes the users and add a DT > > binding doc for the drivers. > > > > Most patches can be applied independently, with the exception of patches > > 2 to 4 that should be applied in the same tree to keep bisect-ability. I > > suggest these to go through the MFD subsystem tree. > > > > Best regards, > > Javier > > > > Are you planning to pick this series? It has been in the list for > months and were resent many times... I think you exaggerate a little. Your last Ack (from Linus) was only collected in v6, which has only been resent once with that Ack applied. =:) We are currently only half way through the merge-window. This patch will be hoovered up during the early -rcs. Please be patient around the time of the merge-window, since Maintainers are either usually very busy with pull-requests, or taking a 2 minute breather before the chaos starts over. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
