summaryrefslogtreecommitdiffstats
path: root/mm/mempolicy.c
diff options
context:
space:
mode:
authorAnton Vorontsov <anton.vorontsov@linaro.org>2012-06-18 19:15:50 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-06-20 16:15:22 -0700
commit924d37118f9e18825294b2012a10c6245d6c25e1 (patch)
tree9cc0169d406efeddab7d149700e0a507718f9864 /mm/mempolicy.c
parent62a1efb9f868690d68b11ffb22dc598e547aa184 (diff)
downloadop-kernel-dev-924d37118f9e18825294b2012a10c6245d6c25e1.zip
op-kernel-dev-924d37118f9e18825294b2012a10c6245d6c25e1.tar.gz
pstore/ram: Probe as early as possible
Registering the platform driver before module_init allows us to log oopses that happen during device probing. This requires changing module_init to postcore_initcall, and switching from platform_driver_probe to platform_driver_register because the platform device is not registered when the platform driver is registered; and because we use driver_register, now can't use create_bundle() (since it will try to register the same driver once again), so we have to switch to platform_device_register_data(). Also, some __init -> __devinit changes were needed. Overall, the registration logic is now much clearer, since we have only one driver registration point, and just an optional dummy device, which is created from the module parameters. Suggested-by: Colin Cross <ccross@android.com> Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org> Acked-by: Kees Cook <keescook@chromium.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm/mempolicy.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud