From: Uwe Kleine-König Date: Fri, 29 Jan 2010 10:40:38 +0000 (+0100) Subject: modpost: members of *driver structs should not point to __init functions X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=b75dcabd6c6c71d7cea64f78b06d18d9cda0ddd1;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git modpost: members of *driver structs should not point to __init functions Either the functions referred to in a driver struct should live in .devinit or the driver should be registered using platform_driver_probe (or equivalent for different driver types) with ->probe being NULL. Signed-off-by: Uwe Kleine-König --- diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c index 20923613467c..713b62eed875 100644 --- a/scripts/mod/modpost.c +++ b/scripts/mod/modpost.c @@ -961,7 +961,7 @@ static int section_mismatch(const char *fromsec, const char *tosec) * Pattern 2: * Many drivers utilise a *driver container with references to * add, remove, probe functions etc. - * These functions may often be marked __init and we do not want to + * These functions may often be marked __devinit and we do not want to * warn here. * the pattern is identified by: * tosec = init or exit section