From: Chanwoo Choi <cw00.choi@samsung.com>
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
Date: Mon, 27 Aug 2012 08:53:50 +0900 [thread overview]
Message-ID: <503AB70E.2000407@samsung.com> (raw)
In-Reply-To: <5037B41C.6040703@xenotime.net>
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.
next prev parent reply other threads:[~2012-08-26 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 7:28 linux-next: Tree for Aug 24 Stephen Rothwell
2012-08-24 17:04 ` [PATCH -next] extcon: extcon-arizona depends on INPUT Randy Dunlap
2012-08-26 23:53 ` Chanwoo Choi [this message]
2012-09-04 23:51 ` Randy Dunlap
2012-09-05 3:28 ` Mark Brown
2012-09-05 19:16 ` Greg KH
2012-09-05 20:18 ` 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=503AB70E.2000407@samsung.com \
--to=cw00.choi@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.