From: Adrian Hunter <adrian.hunter@intel.com>
To: Brian Norris <briannorris@chromium.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: Al Cooper <alcooperx@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-brcmstb: Allow building with COMPILE_TEST
Date: Tue, 25 Oct 2022 14:08:36 +0300 [thread overview]
Message-ID: <8a1549d5-7407-7e47-5fbe-bcb9ca953cda@intel.com> (raw)
In-Reply-To: <20221024181759.2355583-1-briannorris@chromium.org>
On 24/10/22 21:17, Brian Norris wrote:
> This driver is pretty simple, and it can be useful to build it (for
> validation purposes) without BMIPS or ARCH_BRCMSTB.
>
> It technically depends on CONFIG_OF to do anything useful at runtime,
> but it still works out OK for compile-testing using the !OF stubs.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
>
> drivers/mmc/host/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
> index f324daadaf70..453fba8d2d9d 100644
> --- a/drivers/mmc/host/Kconfig
> +++ b/drivers/mmc/host/Kconfig
> @@ -1040,10 +1040,10 @@ config MMC_SDHCI_MICROCHIP_PIC32
>
> config MMC_SDHCI_BRCMSTB
> tristate "Broadcom SDIO/SD/MMC support"
> - depends on ARCH_BRCMSTB || BMIPS_GENERIC
> + depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
> depends on MMC_SDHCI_PLTFM
> select MMC_CQHCI
> - default y
> + default ARCH_BRCMSTB || BMIPS_GENERIC
> help
> This selects support for the SDIO/SD/MMC Host Controller on
> Broadcom STB SoCs.
next prev parent reply other threads:[~2022-10-25 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 18:17 Brian Norris
2022-10-24 18:22 ` Florian Fainelli
2022-10-25 11:08 ` Adrian Hunter [this message]
2022-10-26 11:25 ` Ulf Hansson
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=8a1549d5-7407-7e47-5fbe-bcb9ca953cda@intel.com \
--to=adrian.hunter@intel.com \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=briannorris@chromium.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®