- 30 Apr, 2013 40 commits
-
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
Jingoo Han <jg1.han@samsung.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
Paul Mundt <lethal@linux-sh.org> Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver_probe() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
Other devm_* APIs use 'struct device *dev' as the first argument. Thus, in order to sync with other devm_* functions, struct device is used as the first argument for devm_rtc_device_register(). Signed-off-by:
-
Jingoo Han authored
dev_info()/dev_emerg() are preferred to pr_info()/pr_emerg(). Signed-off-by:
-
Jingoo Han authored
Fix indentation of bit definitions to enhance the readability. Signed-off-by:
-
Jingoo Han authored
Use devm_kzalloc() to make cleanup paths more simple. Signed-off-by:
-
Jingoo Han authored
Add missing module author name to MODULE_AUTHOR macro. Signed-off-by:
-
Jingoo Han authored
Use module_platform_driver() macro which makes the code smaller and simpler. Signed-off-by:
-
Jingoo Han authored
These functions allow the driver core to automatically clean up any allocation made by rtc drivers. Thus it simplifies the error paths. Signed-off-by:
Tejun Heo <tj@kernel.org> Signed-off-by:
-
Jingoo Han authored
When platform_driver_probe() is used, bind/unbind via sysfs is disabled. Thus, __init/__exit annotations can be added to probe()/remove(). Signed-off-by:
-
Jingoo Han authored
When platform_driver_probe() is used, bind/unbind via sysfs is disabled. Thus, __init/__exit annotations can be added to probe()/remove(). Signed-off-by:
-
Jingoo Han authored
When platform_driver_probe() is used, bind/unbind via sysfs is disabled. Thus, __init/__exit annotations can be added to probe()/remove(). Signed-off-by:
-
Jingoo Han authored
When platform_driver_probe() is used, bind/unbind via sysfs is disabled. Thus, __init/__exit annotations can be added to probe()/remove(). Signed-off-by:
-
Jingoo Han authored
When platform_driver_probe() is used, bind/unbind via sysfs is disabled. Thus, __init/__exit annotations can be added to probe()/remove(). Signed-off-by:
-
Jingoo Han authored
When platform_driver_probe() is used, bind/unbind via sysfs is disabled. Thus, __init/__exit annotations can be added to probe()/remove(). Signed-off-by:
-
Jingoo Han authored
When platform_driver_probe() is used, bind/unbind via sysfs is disabled. Thus, __init/__exit annotations can be added to probe()/remove(). Signed-off-by:
-
Andrew Morton authored
Also enables cleanup of some 80-col trickery. Cc: Richard Weinberger <richard@nod.at> Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by:
-
Richard Weinberger authored
If the kernel was booted with the "quiet" boot option we have currently no chance to see why an initrd fails. Change KERN_WARNING to KERN_ERR to see what is going on. Signed-off-by:
Richard Weinberger <richard@nod.at> Cc: "H. Peter Anvin" <hpa@zytor.com> Cc: Rusty Russell <rusty@rustcorp.com.au> Cc: Jim Cromie <jim.cromie@gmail.com> Signed-off-by:
-
Steven Rostedt authored
As I was testing a lot of my code recently, and having several "successes", I accidentally noticed in the dmesg this little line: start_kernel(): bug: interrupts were enabled *very* early, fixing it Sure enough, one of my patches two commits ago enabled interrupts early. The sad part here is that I never noticed it, and I ran several tests with ktest too, and ktest did not notice this line. What ktest looks for (and so does many other automated testing scripts) is a back trace produced by a WARN_ON() or BUG(). As a back trace was never produced, my buggy patch could have slipped into linux-next, or even worse, mainline. Adding a WARN(!irqs_disabled()) makes this bug a little more obvious: PID hash table entries: 4096 (order: 3, 32768 bytes) __ex_table already sorted, skipping sort Checking aperture... No AGP bridge found Calgary: detecting Calgary via BIOS EBDA area Calgary: Unable to locate Rio Grande table in EBDA - bailing! Memory: 2003252k/2054848k available (4857k kernel code, 460k absent, 51136k reserved, 6210k data, 1096k init) ------------[ cut here ]------------ WARNING: at /home/rostedt/work/git/linux-trace.git/init/main.c:543 start_kernel+0x21e/0x415() Hardware name: To Be Filled By O.E.M. Interrupts were enabled *very* early, fixing it Modules linked in: Pid: 0, comm: swapper/0 Not tainted 3.8.0-test+ #286 Call Trace: warn_slowpath_common+0x83/0x9b warn_slowpath_fmt+0x46/0x48 start_kernel+0x21e/0x415 x86_64_start_reservations+0x10e/0x112 x86_64_start_kernel+0x102/0x111 ---[ end trace 007d8b0491b4f5d8 ]--- Preemptible hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. NR_IRQS:4352 nr_irqs:712 16 Console: colour VGA+ 80x25 console [ttyS0] enabled, bootconsole disabled Do you see it? The original version of this patch just slapped a WARN_ON() in there and kept the printk(). Ard van Breemen suggested using the WARN() interface, which makes the code a bit cleaner. Also, while examining other warnings in init/main.c, I found two other locations that deserve a bloody murder scream if their conditions are hit, and updated them accordingly. Signed-off-by:Steven Rostedt <rostedt@goodmis.org> Cc: Ard van Breemen <ard@telegraafnet.nl> Signed-off-by:
-
