From: Randy Dunlap <rdunlap@infradead.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: [PATCH] Fix build without CONFIG_INPUT_LEDS [Was: mmotm 2013-10-29-16-22 uploaded (input)]
Date: Wed, 30 Oct 2013 11:12:08 -0700 [thread overview]
Message-ID: <52714BF8.5040008@infradead.org> (raw)
In-Reply-To: <20131030114624.GY5442@type.youpi.perso.aquilenet.fr>
On 10/30/13 04:46, Samuel Thibault wrote:
> Randy Dunlap, le Tue 29 Oct 2013 18:57:36 -0700, a écrit :
>> arc_ps2.c:(.text+0x500): multiple definition of `input_led_connect'
>
> D'oh. I indeed hadn't tested the inlines, sorry about this.
>
> Andrew, could you add the following patch on top of
> input-route-kbd-leds-through-the-generic-leds-layer.patch
> or perhaps rather fold into it?
>
> Samuel
>
>
>
> Really mark inlines as static inlines, so they are not defined multiple
> times.
>
> Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
>
> --- include/linux/input.h.orig 2013-10-30 12:42:41.169038670 +0100
> +++ include/linux/input.h 2013-10-30 12:42:42.908987157 +0100
> @@ -540,12 +540,12 @@
>
> #else
>
> -int input_led_connect(struct input_dev *dev)
> +static inline int input_led_connect(struct input_dev *dev)
> {
> return 0;
> }
>
> -void input_led_disconnect(struct input_dev *dev)
> +static inline void input_led_disconnect(struct input_dev *dev)
> {
> }
>
> --
--
~Randy
next prev parent reply other threads:[~2013-10-30 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 23:23 mmotm 2013-10-29-16-22 uploaded akpm
2013-10-30 1:57 ` mmotm 2013-10-29-16-22 uploaded (input) Randy Dunlap
2013-10-30 11:46 ` [PATCH] Fix build without CONFIG_INPUT_LEDS [Was: mmotm 2013-10-29-16-22 uploaded (input)] Samuel Thibault
2013-10-30 18:12 ` Randy Dunlap [this message]
2013-10-30 23:20 ` Stephen Rothwell
2013-10-30 23:23 ` Andrew Morton
2013-10-30 23:27 ` Stephen Rothwell
2013-10-30 18:09 ` mmotm 2013-10-29-16-22 uploaded (dm-flakey.c) Randy Dunlap
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=52714BF8.5040008@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
/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).