From: Herve Codina <herve.codina@bootlin.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Derek Kiernan <derek.kiernan@amd.com>,
Dragan Cvetic <dragan.cvetic@amd.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: Kconfig: Make MCHP_LAN966X_PCI depend on OF, not select it
Date: Fri, 29 Nov 2024 18:45:00 +0100 [thread overview]
Message-ID: <20241129184500.6d72a7e1@bootlin.com> (raw)
In-Reply-To: <20241129-lan966x-depend-v1-1-603fc4996c4f@chromium.org>
Hi Ricardo,
On Fri, 29 Nov 2024 10:41:17 +0000
Ricardo Ribalda <ribalda@chromium.org> wrote:
> Most (maybe all?) the drivers depend on OF instead of selecting it. This
> is more convenient for CI because we can have test scripts that do:
> make allyesconfig
> scripts/config -d OF
> make olddefconfig
>
> Without this patch, OF cannot be disabled that way.
>
> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> ---
> drivers/misc/Kconfig | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> index 902c306bc972..2ea5f40ff4e4 100644
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -612,8 +612,7 @@ config MARVELL_CN10K_DPI
>
> config MCHP_LAN966X_PCI
> tristate "Microchip LAN966x PCIe Support"
> - depends on PCI
> - select OF
> + depends on PCI && OF
> select OF_OVERLAY
> select IRQ_DOMAIN
> help
>
> ---
> base-commit: 7af08b57bcb9ebf78675c50069c54125c0a8b795
> change-id: 20241129-lan966x-depend-8bc69b4954e5
>
Not sure it should be done that way (See [1]). Also I pointed out this
patch in the discussion.
[1] https://lore.kernel.org/all/dywwnh7ns47ffndsttstpcsw44avxjvzcddmceha7xavqjdi77@cqdgmpdtywol/
Best regards,
Hervé
next prev parent reply other threads:[~2024-11-29 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 10:41 [PATCH] misc: Kconfig: Make MCHP_LAN966X_PCI depend on OF, not select it Ricardo Ribalda
2024-11-29 17:45 ` Herve Codina [this message]
2024-11-29 17:57 ` Ricardo Ribalda
2024-11-29 18:12 ` Herve Codina
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=20241129184500.6d72a7e1@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=arnd@arndb.de \
--cc=derek.kiernan@amd.com \
--cc=dragan.cvetic@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ribalda@chromium.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