linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: laurentiu.tudor@nxp.com (Laurentiu Tudor)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 8/8] staging: fsl-mc: allow the driver compile multi-arch
Date: Tue, 18 Jul 2017 14:36:07 +0000	[thread overview]
Message-ID: <596E1CD7.1050909@nxp.com> (raw)
In-Reply-To: <CAK8P3a0WvNgk5eXQoPpXiLwOS_wB1NdfCyPtiKMys3qqEwHjDw@mail.gmail.com>

Hi Arnd,

On 07/18/2017 05:25 PM, Arnd Bergmann wrote:
> On Tue, Jul 18, 2017 at 3:37 PM,  <laurentiu.tudor@nxp.com> wrote:
>
>> --- a/drivers/staging/fsl-dpaa2/Kconfig
>> +++ b/drivers/staging/fsl-dpaa2/Kconfig
>> @@ -4,7 +4,7 @@
>>
>>   config FSL_DPAA2
>>          bool "Freescale DPAA2 devices"
>> -       depends on FSL_MC_BUS
>> +       depends on FSL_MC_BUS && ARCH_LAYERSCAPE
>>          ---help---
>>            Build drivers for Freescale DataPath Acceleration
>>            Architecture (DPAA2) family of SoCs.
>
> I would probably leave the dependency in there conditionally, like
>
>           depends on ARCH_LAYERSCAPE || COMPILE_TEST
>
> That way, we can build the driver on all architectures with "make allmodconfig"
> or "make randconfig", but regular users that disable COMPILE_TEST
> won't be bothered by the extra config options unless they have the
> right hardware.
>

Good point, I'll take care of it. But don't you mean COMPILE_TEST be 
added on the actual MC_BUS config, like so:

  config FSL_MC_BUS
  	bool "QorIQ DPAA2 fsl-mc bus driver"
-	depends on OF && ARCH_LAYERSCAPE
+	depends on OF && (ARCH_LAYERSCAPE || COMPILE_TEST)
  	select GENERIC_MSI_IRQ_DOMAIN
?

The other drivers that depend on the MC_BUS won't compile on other 
architectures.

---
Thanks & Best Regards, Laurentiu

  reply	other threads:[~2017-07-18 14:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 13:37 [PATCH v2 0/7] staging: fsl-mc: make the driver compile on other architectures laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 1/8] staging: fsl-mc: add missing fsl_mc comment in struct msi_desc laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 2/8] staging: fsl-mc: use generic memory barriers laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 3/8] staging: fsl-mc: drop useless gic v3 related #include laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 4/8] staging: fsl-mc: fix compilation with non-generic msi domain ops laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 5/8] staging: fsl-mc: fix formating of phys_addr_t on 32 bits laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 6/8] staging: fsl-mc: don't use raw device io functions laurentiu.tudor at nxp.com
2017-07-18 14:18   ` Arnd Bergmann
2017-07-18 14:26     ` Laurentiu Tudor
2017-07-18 14:28       ` Arnd Bergmann
2017-07-18 13:37 ` [PATCH v2 7/8] staging: fsl-mc: make the driver compile on 32-bit laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 8/8] staging: fsl-mc: allow the driver compile multi-arch laurentiu.tudor at nxp.com
2017-07-18 14:25   ` Arnd Bergmann
2017-07-18 14:36     ` Laurentiu Tudor [this message]
2017-07-18 14:39       ` Arnd Bergmann
2017-07-18 14:26 ` [PATCH v2 0/7] staging: fsl-mc: make the driver compile on other architectures Arnd Bergmann
2017-07-18 14:43   ` Laurentiu Tudor

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=596E1CD7.1050909@nxp.com \
    --to=laurentiu.tudor@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).