Thread (3 messages) 3 messages, 1 author, 2013-08-12
STALE4685d

[PATCH 1/3] Input: wistron_btns - Fix incorrect placement of __initconst

From: Sachin Kamat <hidden>
Date: 2013-08-12 09:50:19
Subsystem: input (keyboard, mouse, joystick, touchscreen) drivers, the rest, wistron laptop button driver · Maintainers: Dmitry Torokhov, Linus Torvalds, Miloslav Trmac

__initconst should be placed between the variable name and equal
sign for the variable to be placed in the intended section.

Signed-off-by: Sachin Kamat <redacted>
Cc: Miloslav Trmac <mitr@volny.cz>
---
 drivers/input/misc/wistron_btns.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/misc/wistron_btns.c b/drivers/input/misc/wistron_btns.c
index 56536f4b9..35c33c6 100644
--- a/drivers/input/misc/wistron_btns.c
+++ b/drivers/input/misc/wistron_btns.c
@@ -635,7 +635,7 @@ static struct key_entry keymap_prestigio[] __initdata = {
  * a list of buttons and their key codes (reported when loading this module
  * with force=1) and the output of dmidecode to $MODULE_AUTHOR.
  */
-static const struct dmi_system_id __initconst dmi_ids[] = {
+static const struct dmi_system_id dmi_ids[] __initconst = {
 	{
 		/* Fujitsu-Siemens Amilo Pro V2000 */
 		.callback = dmi_matched,
-- 
1.7.9.5
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help