Re: [PATCH 12/19] pinctrl: exynos: don't mark probing functions as __init

2013-01-29 Thread Linus Walleij
On Fri, Jan 25, 2013 at 3:14 PM, Arnd Bergmann wrote: > Functions called from a driver probe() method must not be > marked __init, because they may get called after the > init phase is done, when the device shows up late, or > because of deferred probing. > > Without this patch, building exynos_d

[PATCH 12/19] pinctrl: exynos: don't mark probing functions as __init

2013-01-25 Thread Arnd Bergmann
Functions called from a driver probe() method must not be marked __init, because they may get called after the init phase is done, when the device shows up late, or because of deferred probing. Without this patch, building exynos_defconfig results in multiple warnings like: WARNING: drivers/pinct

RE: [PATCH 12/19] pinctrl: exynos: don't mark probing functions as __init

2013-01-25 Thread Kukjin Kim
Arnd Bergmann wrote: > > Functions called from a driver probe() method must not be > marked __init, because they may get called after the > init phase is done, when the device shows up late, or > because of deferred probing. > > Without this patch, building exynos_defconfig results in > multiple

[PATCH 12/19] pinctrl: exynos: don't mark probing functions as __init

2013-01-25 Thread Arnd Bergmann
Functions called from a driver probe() method must not be marked __init, because they may get called after the init phase is done, when the device shows up late, or because of deferred probing. Without this patch, building exynos_defconfig results in multiple warnings like: WARNING: drivers/pinct