linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bamvor Zhang Jian <bamvor.zhangjian@linaro.org>
To: Fathi Boudra <fathi.boudra@linaro.org>
Cc: linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] selftests: gpio: add config fragment for gpio-mockup
Date: Tue, 4 Apr 2017 08:52:39 +0800	[thread overview]
Message-ID: <CAFy1USSHd0hMV_ws12dPEeEPbgKFcNiS_g6ApED68rWv-5daeQ@mail.gmail.com> (raw)
In-Reply-To: <20170331084130.7973-1-fathi.boudra@linaro.org>

Hi,

On 31 March 2017 at 16:41, Fathi Boudra <fathi.boudra@linaro.org> wrote:
> The gpio test requires to insert the gpio mockup module (CONFIG_GPIO_MOCKUP).
> The gpio mockup driver depends on gpiolib (CONFIG_GPIOLIB).
> CONFIG_GPIO_SYSFS is selected automatically by the gpio mockup driver.
>
> Tested on x86_64 and arm64 with defconfig and kselftest-merge.
>
> Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Reviewed-by: Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>
> ---
>
> Changes in v2:
>  * Per Bamvor Zhang Jian review, add gpiolib dependency (CONFIG_GPIOLIB).
>    Skipped CONFIG_DEBUG_GPIO as it isn't necessary, and CONFIG_GPIO_SYSFS
>    as it's selected automatically by the gpio mockup driver.
>
>  tools/testing/selftests/gpio/config | 2 ++
>  1 file changed, 2 insertions(+)
>  create mode 100644 tools/testing/selftests/gpio/config
>
> diff --git a/tools/testing/selftests/gpio/config b/tools/testing/selftests/gpio/config
> new file mode 100644
> index 000000000000..abaa6902b7b6
> --- /dev/null
> +++ b/tools/testing/selftests/gpio/config
> @@ -0,0 +1,2 @@
> +CONFIG_GPIOLIB=y
> +CONFIG_GPIO_MOCKUP=m
> --
> 2.11.0

  reply	other threads:[~2017-04-04  0:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31  8:41 Fathi Boudra
2017-04-04  0:52 ` Bamvor Zhang Jian [this message]
2017-04-19 17:32   ` Fathi Boudra
2017-04-27 13:46     ` Shuah Khan

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=CAFy1USSHd0hMV_ws12dPEeEPbgKFcNiS_g6ApED68rWv-5daeQ@mail.gmail.com \
    --to=bamvor.zhangjian@linaro.org \
    --cc=fathi.boudra@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --subject='Re: [PATCH v2] selftests: gpio: add config fragment for gpio-mockup' \
    /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

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).