From: Florian Fainelli <f.fainelli@gmail.com>
To: Marc Zyngier <maz@kernel.org>
Cc: linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] irqchip: Allow test compilation of Broadcom drivers
Date: Sun, 27 Nov 2022 12:28:39 -0800 [thread overview]
Message-ID: <9c403170-4493-d960-b470-ba337dae893d@gmail.com> (raw)
In-Reply-To: <87tu2lu9rc.wl-maz@kernel.org>
On 11/26/2022 5:26 AM, Marc Zyngier wrote:
> On Mon, 24 Oct 2022 23:27:39 +0100,
> Florian Fainelli <f.fainelli@gmail.com> wrote:
>>
>> Allow test compilation of the Broadcom irqchip drivers by adding a
>> COMPILE_TEST dependency.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> drivers/irqchip/Kconfig | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
>> index 7ef9f5e696d3..e4b2ec9b2450 100644
>> --- a/drivers/irqchip/Kconfig
>> +++ b/drivers/irqchip/Kconfig
>> @@ -116,7 +116,7 @@ config BCM6345_L1_IRQ
>>
>> config BCM7038_L1_IRQ
>> tristate "Broadcom STB 7038-style L1/L2 interrupt controller driver"
>> - depends on ARCH_BRCMSTB || BMIPS_GENERIC
>> + depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
>
> Do we actually need all this churn now that OF is user-selectable (see
> 0166dc11be91)?
Seems to me that we would since that allows people to choose the
building of these drivers rather than lift the dependencies and replace
it with:
depends on OF
as this would prompt many users about drivers they do not care about.
--
Florian
prev parent reply other threads:[~2022-11-27 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 22:27 [PATCH] irqchip: Allow test compilation of Broadcom drivers Florian Fainelli
2022-11-26 13:26 ` Marc Zyngier
2022-11-27 20:28 ` Florian Fainelli [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=9c403170-4493-d960-b470-ba337dae893d@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
/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