From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH 1/2] Input: migor-ts - allow driver to build if COMPILE_TEST is enabled
Date: Thu, 19 May 2016 09:34:19 -0700 [thread overview]
Message-ID: <20160519163419.GD38800@dtor-ws> (raw)
In-Reply-To: <1463502759-14393-1-git-send-email-javier@osg.samsung.com>
On Tue, May 17, 2016 at 12:32:37PM -0400, Javier Martinez Canillas wrote:
> The driver only has runtime but no build time dependency with SH_MIGOR, so
> it can be built for testing purposes if the COMPILE_TEST option is enabled.
>
> This is useful to have more build coverage and make sure that drivers are
> not affected by changes that could cause build regressions.
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
Applied, thank you.
> ---
>
> drivers/input/touchscreen/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/touchscreen/Kconfig b/drivers/input/touchscreen/Kconfig
> index 8ecdc38fd489..9f6f001ccf07 100644
> --- a/drivers/input/touchscreen/Kconfig
> +++ b/drivers/input/touchscreen/Kconfig
> @@ -632,7 +632,7 @@ config TOUCHSCREEN_EDT_FT5X06
>
> config TOUCHSCREEN_MIGOR
> tristate "Renesas MIGO-R touchscreen"
> - depends on SH_MIGOR && I2C
> + depends on (SH_MIGOR || COMPILE_TEST) && I2C
> help
> Say Y here to enable MIGO-R touchscreen support.
>
> --
> 2.5.5
>
--
Dmitry
prev parent reply other threads:[~2016-05-19 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 16:32 [PATCH 1/2] Input: migor-ts - allow driver to build if COMPILE_TEST is enabled Javier Martinez Canillas
2016-05-17 16:32 ` [PATCH 2/2] Input: migor-ts - fix error for modular build Javier Martinez Canillas
2016-05-19 16:34 ` Dmitry Torokhov
2016-05-19 16:34 ` 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=20160519163419.GD38800@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=javier@osg.samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@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