On 05/22/2013 01:56 AM, Linus Walleij wrote: > On Mon, May 13, 2013 at 10:18 PM, Linus Walleij > <linus.walleij@xxxxxxxxxx> wrote: > >> This tries to address an issue found when writing an MFD driver >> for the Nomadik STw481x PMICs: as the platform is using device >> tree exclusively I want to specify the driver matching like >> this: > (...) >> --- >> ChangeLog v1->v2: >> - Use of_match_device() to determine if there is a DT match in >> the probe code. If there is a match we pass NULL for the >> id_table match parameter. > > Ping on this. > > v2 should be doing what Grant suggested... This has just shown up in next-20130617, and breaks at least the TPS65910 and TPS62360 drivers, since they assume that the id parameter passed to probe is non-NULL. However, now the parameter is NULL since these drivers have both an ID table and an OF match table. I'd like to suggest this patch be reverted an re-introduced immediately after the merge window. That should give enough time for everyone to get a heads-up on fixing any drivers with a similar problem, rather than trying to cram all that in immediately before the merge window. I'd also suggest that this patch should be accompanied by fixes for any similarly broken drivers, based on code inspection. Do people agree? If not, please let us know ASAP so we can post patches to fix this. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
