linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Wan ZongShun <mcuos.com@gmail.com>
Cc: Jean Delvare <jdelvare@suse.de>,
	linux-input@vger.kernel.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Input: w90p910_ts - depend on ARCH_W90X900
Date: Sat, 19 Apr 2014 22:38:56 -0700	[thread overview]
Message-ID: <20140420053856.GF12454@core.coreip.homeip.net> (raw)
In-Reply-To: <CAKT61h__8fuJDs94akU73grWns82+mk1vmSdQw5fwd1Cx-455g@mail.gmail.com>

On Tue, Apr 01, 2014 at 09:17:03PM +0800, Wan ZongShun wrote:
> ---------- Forwarded message ----------
> From: Jean Delvare <jdelvare@suse.de>
> Date: 2014-04-01 20:20 GMT+08:00
> Subject: [PATCH] Input: w90p910_ts - depend on ARCH_W90X900
> To: linux-input@vger.kernel.org, linux-arm-kernel@lists.infradead.org
> 抄送: Wan ZongShun <mcuos.com@gmail.com>, Dmitry Torokhov
> <dmitry.torokhov@gmail.com>
> 
> 
> The w90p910_ts touchscreen driver is heavily architecture dependent,
> so there is no point in letting it be built on other architectures
> than it was written for.
> 
> All other W90P910/W90X900 drivers already have that dependency, so it
> makes things more consistent and configuration easier.
> 
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Cc: Wan ZongShun <mcuos.com@gmail.com>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
>  drivers/input/touchscreen/Kconfig |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-3.14-rc8.orig/drivers/input/touchscreen/Kconfig
> 2014-02-09 16:53:02.945634113 +0100
> +++ linux-3.14-rc8/drivers/input/touchscreen/Kconfig    2014-04-01
> 14:10:08.936933702 +0200
> @@ -867,7 +867,7 @@ config TOUCHSCREEN_TSC2007
> 
>  config TOUCHSCREEN_W90X900
>         tristate "W90P910 touchscreen driver"
> -       depends on HAVE_CLK
> +       depends on ARCH_W90X900
>         help
>           Say Y here if you have a W90P910 based touchscreen.
> 
> Sure, your idea is reasonable.
> 
> Acked-by Wan Zongshun <mcuos.com@gmail.com>

Applied, thank you.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-04-20  5:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 12:20 [PATCH] Input: w90p910_ts - depend on ARCH_W90X900 Jean Delvare
2014-04-01 13:17 ` Wan ZongShun
2014-04-20  5:38   ` Dmitry Torokhov [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=20140420053856.GF12454@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=jdelvare@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=mcuos.com@gmail.com \
    /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).