From: Randy Dunlap <rdunlap@infradead.org>
To: Luis de Bethencourt <luisbg@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: JBottomley@odin.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: kconfig: When possible, compile drivers with COMPILE_TEST
Date: Wed, 14 Oct 2015 15:25:05 -0700 [thread overview]
Message-ID: <561ED641.9090208@infradead.org> (raw)
In-Reply-To: <1444857220-26595-1-git-send-email-luisbg@osg.samsung.com>
On 10/14/15 14:13, Luis de Bethencourt wrote:
> These drivers only have runtime but no build time dependencies, so they can
> be built for testing purposes if the Kconfig 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: Luis de Bethencourt <luisbg@osg.samsung.com>
> ---
> drivers/scsi/Kconfig | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
> index d2f480b..0d8ee16 100644
> --- a/drivers/scsi/Kconfig
> +++ b/drivers/scsi/Kconfig
> @@ -1238,7 +1238,7 @@ config SCSI_NCR53C8XX_NO_DISCONNECT
>
> config SCSI_PAS16
> tristate "PAS16 SCSI support"
> - depends on ISA && SCSI
> + depends on (ISA || COMPILE) && SCSI
COMPILE_TEST
> select SCSI_SPI_ATTRS
> ---help---
> This is support for a SCSI host adapter. It is explained in section
--
~Randy
next prev parent reply other threads:[~2015-10-14 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 21:13 [PATCH] scsi: kconfig: When possible, compile drivers with COMPILE_TEST Luis de Bethencourt
2015-10-14 22:25 ` Randy Dunlap [this message]
2015-10-14 22:42 ` James Bottomley
2015-10-14 23:30 ` Luis de Bethencourt
2015-10-14 23:39 ` James Bottomley
2015-10-16 13:08 ` Luis de Bethencourt
2015-10-15 1:11 ` kbuild test robot
2015-10-15 1:11 ` kbuild test robot
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=561ED641.9090208@infradead.org \
--to=rdunlap@infradead.org \
--cc=JBottomley@odin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luisbg@osg.samsung.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 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.