Re: [PATCH] vesafb: use platform_driver_probe() instead ofplatform_driver_register()

From: Uwe Kleine-König
Date: Sat Mar 27 2010 - 10:18:58 EST


Hello Jan,

On Fri, Mar 26, 2010 at 04:48:33PM +0000, Jan Beulich wrote:
> Commit c2e13037e6794bd0d9de3f9ecabf5615f15c160b introduced a huge
> amount of section mismatch warnings in vesafb code. Rather than
> converting all of the annotations, do the obvious and revert the
> __init -> __devinit change, and use the recommended (in that patch)
> alternative to calling platform_driver_register(): vesafb depends on
> information obtained from by kernel at boot time, cannot be a module,
> and no post-boot devices can ever show up.
>
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
Looks good, Acked-by: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>

Thanks
Uwe

--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/