From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
John Crispin <blogic@openwrt.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] next: input: Fix build error seen if input-core is built as module
Date: Mon, 3 Nov 2014 09:30:47 +0100 [thread overview]
Message-ID: <20141103083046.GA10653@type.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <1414993997-19179-1-git-send-email-linux@roeck-us.net>
Hello,
Guenter Roeck, le Sun 02 Nov 2014 21:53:17 -0800, a écrit :
> The following build error may be seen if input-core is built as module:
>
> drivers/input/leds.o: In function `init_module':
> leds.c:(.init.text+0x0): multiple definition of `init_module'
> drivers/input/input.o:input.c:(.init.text+0x0): first defined here
> drivers/input/leds.o: In function `cleanup_module':
> leds.c:(.exit.text+0x0): multiple definition of `cleanup_module'
> drivers/input/input.o:input.c:(.exit.text+0x0): first defined here
> make[2]: *** [drivers/input/input-core.o] Error 1
I have already submitted a patch to fix it, here it is again:
Now that input/leds.c is compiled into the input.ko module in the mm
tree, its init and exit function must be called by input.ko's init and
exit functions, instead of duplicating the module init/exit hooks, which
leads to the following build error when input is built as a module:
leds.c:(.init.text+0x0): multiple definition of `init_module'
leds.c:(.exit.text+0x0): multiple definition of `cleanup_module'
This also adds a proper clean of the vt_led_work queues in the exit
function.
Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
---
This is a follow-up to the following reports:
Re: [next:master 9776/10302] leds.c:(.init.text+0x0): multiple definition of `init_module'
Re: [next:master 9391/10970] leds.c:(.exit.text+0x0): multiple definition of `cleanup_module'
and to be applied over the existing
input-route-kbd-leds-through-the-generic-leds-layer-fix-2
please.
Thanks!
Samuel
--- a/drivers/input/input.c
+++ b/drivers/input/input.c
@@ -2427,6 +2427,8 @@ static int __init input_init(void)
goto fail2;
}
+ input_led_init();
+
return 0;
fail2: input_proc_exit();
@@ -2436,6 +2438,7 @@ static int __init input_init(void)
static void __exit input_exit(void)
{
+ input_led_exit();
input_proc_exit();
unregister_chrdev_region(MKDEV(INPUT_MAJOR, 0),
INPUT_MAX_CHAR_DEVICES);
--- a/drivers/input/leds.c
+++ b/drivers/input/leds.c
@@ -255,22 +255,18 @@ void input_led_disconnect(struct input_d
mutex_unlock(&vt_led_registered_lock);
}
-static int __init input_led_init(void)
+void __init input_led_init(void)
{
unsigned i;
for (i = 0; i < LED_CNT; i++)
INIT_WORK(&vt_led_work[i], vt_led_cb);
-
- return 0;
}
-static void __exit input_led_exit(void)
+void __exit input_led_exit(void)
{
-}
+ unsigned i;
-MODULE_LICENSE("GPL");
-MODULE_DESCRIPTION("User LED support for input layer");
-MODULE_AUTHOR("Samuel Thibault <samuel.thibault@ens-lyon.org>");
-module_init(input_led_init);
-module_exit(input_led_exit);
+ for (i = 0; i < LED_CNT; i++)
+ cancel_work_sync(&vt_led_work[i]);
+}
--- a/include/linux/input.h
+++ b/include/linux/input.h
@@ -536,11 +536,18 @@ int input_ff_create_memless(struct input
#ifdef CONFIG_INPUT_LEDS
+void input_led_init(void);
+void input_led_exit(void);
+
int input_led_connect(struct input_dev *dev);
void input_led_disconnect(struct input_dev *dev);
#else
+static inline void input_led_init(void) { }
+
+static inline void input_led_exit(void) { }
+
static inline int input_led_connect(struct input_dev *dev)
{
return 0;
prev parent reply other threads:[~2014-11-03 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 5:53 [PATCH] next: input: Fix build error seen if input-core is built as module Guenter Roeck
2014-11-03 8:30 ` Samuel Thibault [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141103083046.GA10653@type.youpi.perso.aquilenet.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=akpm@linux-foundation.org \
--cc=blogic@openwrt.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).