Hi, On Tue, Oct 20, 2015 at 7:46 PM, kbuild test robot <[email protected]> wrote: > Hi Doug, > > [auto build test ERROR on pinctrl/for-next -- if it's inappropriate base, > please suggest rules for selecting the more suitable base] > > url: > https://github.com/0day-ci/linux/commits/Douglas-Anderson/drivers-pinctrl-Add-the-concept-of-an-init-state/20151021-101131 > config: i386-randconfig-x004-10191220 (attached as .config) > reproduce: > # save the attached .config to linux build tree > make ARCH=i386 > > All errors (new ones prefixed by >>): > > drivers/base/dd.c: In function 'really_probe': >>> drivers/base/dd.c:325:2: error: implicit declaration of function >>> 'pinctrl_init_done' [-Werror=implicit-function-declaration] > pinctrl_init_done(dev); > ^ > cc1: some warnings being treated as errors > > vim +/pinctrl_init_done +325 drivers/base/dd.c > > 319 } else if (drv->probe) { > 320 ret = drv->probe(dev); > 321 if (ret) > 322 goto probe_failed; > 323 } > 324 > > 325 pinctrl_init_done(dev); > 326 > 327 if (dev->pm_domain && dev->pm_domain->sync) > 328 dev->pm_domain->sync(dev);
Yup, good catch Mr. Robot. I think I've got it all fixed up in: https://patchwork.kernel.org/patch/7454311/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
