From: Simon Horman <horms@kernel.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: Keguang Zhang <keguang.zhang@gmail.com>,
linux-mips@vger.kernel.org, netdev@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: |PATCH] stmmac: dwmac-loongson: Add architecture dependency
Date: Mon, 13 Nov 2023 18:01:07 +0000 [thread overview]
Message-ID: <20231113180107.GA52493@kernel.org> (raw)
In-Reply-To: <20231113154522.0bca3521@endymion.delvare>
On Mon, Nov 13, 2023 at 03:45:22PM +0100, Jean Delvare wrote:
> Only present the DWMAC_LOONGSON option on architectures where it can
> actually be used.
>
> This follows the same logic as the DWMAC_INTEL option.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Cc: Keguang Zhang <keguang.zhang@gmail.com>
> ---
> I'm not familiar with the hardware, so please let me know if the
> dependency needs to be adjusted somehow.
>
> drivers/net/ethernet/stmicro/stmmac/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-6.6.orig/drivers/net/ethernet/stmicro/stmmac/Kconfig
> +++ linux-6.6/drivers/net/ethernet/stmicro/stmmac/Kconfig
> @@ -269,7 +269,7 @@ config DWMAC_INTEL
> config DWMAC_LOONGSON
> tristate "Loongson PCI DWMAC support"
> default MACH_LOONGSON64
> - depends on STMMAC_ETH && PCI
> + depends on MACH_LOONGSON64 && STMMAC_ETH && PCI
Hi Jean,
Could we consider also allowing the build to occur if COMPILE_TEST is set?
This would maintain the current level of build test coverage.
Something line this (completely untested!):
depends on (MACH_LOONGSON64 || COMPILE_TEST) && STMMAC_ETH && PCI
> depends on COMMON_CLK
> help
> This selects the LOONGSON PCI bus support for the stmmac driver,
>
>
> --
> Jean Delvare
> SUSE L3 Support
>
next prev parent reply other threads:[~2023-11-13 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 14:45 |PATCH] stmmac: dwmac-loongson: Add architecture dependency Jean Delvare
2023-11-13 18:01 ` Simon Horman [this message]
2023-11-13 18:33 ` Jean Delvare
2023-11-14 19:49 ` Simon Horman
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=20231113180107.GA52493@kernel.org \
--to=horms@kernel.org \
--cc=jdelvare@suse.de \
--cc=keguang.zhang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=netdev@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 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).