From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Ray Jui <rjui@broadcom.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
bcm-kernel-feedback-list@broadcom.com,
linux-gpio <linux-gpio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Xuefeng Li <lixuefeng@loongson.cn>
Subject: Re: [PATCH 3/3] gpio: pxa: Add COMPILE_TEST support
Date: Mon, 25 May 2020 11:15:47 +0200 [thread overview]
Message-ID: <CAMpxmJW9po_hp64yV73R4fLMQ3_5SbJuvE7Rva8hOvzjAFVHrA@mail.gmail.com> (raw)
In-Reply-To: <1590120740-22912-3-git-send-email-yangtiezhu@loongson.cn>
pt., 22 maj 2020 o 06:12 Tiezhu Yang <yangtiezhu@loongson.cn> napisał(a):
>
> Add COMPILE_TEST support to the PXA GPIO driver for better compile
> testing coverage.
>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
> drivers/gpio/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index 03c01f4..5e90aad 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -439,7 +439,7 @@ config GPIO_PMIC_EIC_SPRD
>
> config GPIO_PXA
> bool "PXA GPIO support"
> - depends on ARCH_PXA || ARCH_MMP
> + depends on ARCH_PXA || ARCH_MMP || COMPILE_TEST
> help
> Say yes here to support the PXA GPIO device
>
> --
> 2.1.0
>
Patch applied.
Bart
next prev parent reply other threads:[~2020-05-25 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 4:12 [PATCH 1/3] gpio: bcm-kona: Fix return value of bcm_kona_gpio_probe() Tiezhu Yang
2020-05-22 4:12 ` [PATCH 2/3] gpio: pxa: Fix return value of pxa_gpio_probe() Tiezhu Yang
2020-05-22 19:07 ` Robert Jarzmik
2020-05-23 3:24 ` Tiezhu Yang
2020-05-25 9:14 ` Bartosz Golaszewski
2020-05-27 18:26 ` Robert Jarzmik
2020-05-22 4:12 ` [PATCH 3/3] gpio: pxa: Add COMPILE_TEST support Tiezhu Yang
2020-05-25 9:15 ` Bartosz Golaszewski [this message]
2020-05-25 9:16 ` [PATCH 1/3] gpio: bcm-kona: Fix return value of bcm_kona_gpio_probe() Bartosz Golaszewski
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=CAMpxmJW9po_hp64yV73R4fLMQ3_5SbJuvE7Rva8hOvzjAFVHrA@mail.gmail.com \
--to=bgolaszewski@baylibre.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=rjui@broadcom.com \
--cc=robert.jarzmik@free.fr \
--cc=yangtiezhu@loongson.cn \
/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).