From: Lee Jones <lee.jones@linaro.org>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: abx500-core: Allow driver to built if COMPILE_TEST is enabled
Date: Wed, 26 Oct 2016 13:37:29 +0100 [thread overview]
Message-ID: <20161026123729.GD11267@dell> (raw)
In-Reply-To: <1476449852-19973-1-git-send-email-javier@osg.samsung.com>
On Fri, 14 Oct 2016, Javier Martinez Canillas wrote:
> The driver only has runtime but no build time dependency with ARCH_U300 ||
> ARCH_U8500 So it can be built for testing purposes if COMPILE_TEST option
> is enabled.
>
> This is useful to have more build coverage and make sure that the driver
> is not affected by changes that could cause build regressions.
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> ---
>
> drivers/mfd/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index c6df6442ba2b..3eb97893a377 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -955,7 +955,7 @@ config MFD_SMSC
>
> config ABX500_CORE
> bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
> - default y if ARCH_U300 || ARCH_U8500
> + default y if ARCH_U300 || ARCH_U8500 || COMPILE_TEST
> help
> Say yes here if you have the ABX500 Mixed Signal IC family
> chips. This core driver expose register access functions.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2016-10-26 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 12:57 [PATCH] mfd: abx500-core: Allow driver to built if COMPILE_TEST is enabled Javier Martinez Canillas
2016-10-26 12:37 ` Lee Jones [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=20161026123729.GD11267@dell \
--to=lee.jones@linaro.org \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
/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.