The patch titled
Subject: cs5535-mfgpt: don't call __init function from __devinit
has been added to the -mm tree. Its filename is
cs5535-mfgpt-dont-call-__init-function-from-__devinit.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Danny Kukawka <danny.kukawka@xxxxxxxxx>
Subject: cs5535-mfgpt: don't call __init function from __devinit
Fix and reset_all_timers() to be __devinit and not __init since the
function gets called from cs5535_mfgpt_probe which is __devinit.
Signed-off-by: Danny Kukawka <danny.kukawka@xxxxxxxxx>
Acked-by: Andres Salomon <dilinger@xxxxxxxxxx>
Cc: Greg KH <greg@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/misc/cs5535-mfgpt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/misc/cs5535-mfgpt.c~cs5535-mfgpt-dont-call-__init-function-from-__devinit drivers/misc/cs5535-mfgpt.c
--- a/drivers/misc/cs5535-mfgpt.c~cs5535-mfgpt-dont-call-__init-function-from-__devinit
+++ a/drivers/misc/cs5535-mfgpt.c
@@ -246,7 +246,7 @@ EXPORT_SYMBOL_GPL(cs5535_mfgpt_write);
* Jordan tells me that he and Mitch once played w/ it, but it's unclear
* what the results of that were (and they experienced some instability).
*/
-static void __init reset_all_timers(void)
+static void __devinit reset_all_timers(void)
{
uint32_t val, dummy;
_
Subject: Subject: cs5535-mfgpt: don't call __init function from __devinit
Patches currently in -mm which might be from danny.kukawka@xxxxxxxxx are
linux-next.patch
cs5535-mfgpt-dont-call-__init-function-from-__devinit.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
