Message-id: <503AB70E.2000407@samsung.com>
Date: Mon, 27 Aug 2012 08:53:50 +0900
From: Chanwoo Choi <cw00.choi@samsung.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216
 Thunderbird/10.0.2
MIME-version: 1.0
To: Randy Dunlap <rdunlap@xenotime.net>, Greg KH <gregkh@linuxfoundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org,
        LKML <linux-kernel@vger.kernel.org>,
        MyungJoo Ham <myungjoo.ham@samsung.com>,
        Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH -next] extcon: extcon-arizona depends on INPUT
References: <20120824172820.ee0f412d2944b08789414207@canb.auug.org.au>
 <5037B41C.6040703@xenotime.net>
In-reply-to: <5037B41C.6040703@xenotime.net>
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1309
Lines: 32

On 08/25/2012 02:04 AM, Randy Dunlap wrote:

> From: Randy Dunlap <rdunlap@xenotime.net>
> 
> extcon-arizona uses input_*() functions so it should depend
> on INPUT.
> 
> ERROR: "input_event" [drivers/extcon/extcon-arizona.ko] undefined!
> ERROR: "input_free_device" [drivers/extcon/extcon-arizona.ko] undefined!
> ERROR: "input_register_device" [drivers/extcon/extcon-arizona.ko] undefined!
> ERROR: "input_set_capability" [drivers/extcon/extcon-arizona.ko] undefined!
> ERROR: "input_allocate_device" [drivers/extcon/extcon-arizona.ko] undefined!
> ERROR: "input_unregister_device" [drivers/extcon/extcon-arizona.ko] undefined!
> 
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> Cc: Chanwoo Choi <cw00.choi@samsung.com>
> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---

Thanks much,

Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>

I will apply this patch to
http://10.90.51.51/cgi-bin/gitweb.cgi?p=linux-samsung;a=shortlog;h=refs/heads/extcon-for-next
and you can check it after some hours.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/