From: Claudiu Beznea <claudiu.beznea@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: wsa+renesas@sang-engineering.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 3/9] PCI: rzg3s-host: Select PCI_HOST_COMMON
Date: Mon, 5 Oct 2026 16:50:41 +0300 [thread overview]
Message-ID: <f5144b5b-0890-4c19-9e0b-1c8a7b462233@kernel.org> (raw)
In-Reply-To: <20261002112227.DB32A1F000FF@smtp.kernel.org>
On 10/2/26 14:22, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] Kconfig: unnecessary selection of PCI_HOST_COMMON causes kernel bloat
> --
>
> commit 45902cd2b000fac7ca52cf6e5a8c266554c39e27
> Author: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> PCI: rzg3s-host: Select PCI_HOST_COMMON
>
> This commit adds a select for PCI_HOST_COMMON to the PCIE_RENESAS_RZG3S_HOST
> kconfig option. It states this is needed for pci_host_common_link_train_delay()
> to avoid build failures.
>
>> diff --git a/drivers/pci/controller/Kconfig b/drivers/pci/controller/Kconfig
>> index d246bbe37948e..3e2889a7f1a09 100644
>> --- a/drivers/pci/controller/Kconfig
>> +++ b/drivers/pci/controller/Kconfig
>> @@ -296,6 +296,7 @@ config PCIE_RENESAS_RZG3S_HOST
>> depends on ARCH_RENESAS || COMPILE_TEST
>> select MFD_SYSCON
>> select IRQ_MSI_LIB
>> + select PCI_HOST_COMMON
>
> [Severity: Medium]
> Is this select actually required for the build?
>
> The commit message notes that pci_host_common_link_train_delay() depends on
> PCI_HOST_COMMON. However, looking at the header,
> pci_host_common_link_train_delay() is implemented as a static inline function
> entirely within pci-host-common.h and only requires linux/delay.h. There
> doesn't appear to be any link dependency on pci-host-common.c.
That's true. I did a mistake here. I should have select this flag on patch 9
which uses pci_host_handle_link_down().
>
> Since selecting a tristate from a bool config forces PCI_HOST_COMMON and
> PCI_ECAM to be built-in rather than modules, could this be pulling in
> unneeded infrastructure and unnecessarily increasing the vmlinux size?
>
>> help
>> Say Y here if you want PCIe host controller support on Renesas RZ/G3S
>> SoC.
>
next prev parent reply other threads:[~2026-10-05 13:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 11:09 [PATCH v5 0/9] PCI: rzg3s-host: Add PCIe hotplug support Claudiu Beznea
2026-10-02 11:09 ` [PATCH v5 1/9] PCI: rzg3s-host: Follow hardware manual clock/reset initialization order Claudiu Beznea
2026-10-02 11:23 ` sashiko-bot
2026-10-02 11:09 ` [PATCH v5 2/9] PCI: rzg3s-host: Fix runtime PM handling in the NOIRQ suspend/resume phase Claudiu Beznea
2026-10-02 11:18 ` sashiko-bot
2026-10-02 11:09 ` [PATCH v5 3/9] PCI: rzg3s-host: Select PCI_HOST_COMMON Claudiu Beznea
2026-10-02 11:22 ` sashiko-bot
2026-10-05 13:50 ` Claudiu Beznea [this message]
2026-10-02 11:09 ` [PATCH v5 4/9] PCI: rzg3s-host: Drop nop instructions Claudiu Beznea
2026-10-02 11:17 ` sashiko-bot
2026-10-02 11:09 ` [PATCH v5 5/9] PCI: rzg3s-host: Move host configuration code together Claudiu Beznea
2026-10-02 11:20 ` sashiko-bot
2026-10-02 11:09 ` [PATCH v5 6/9] PCI: rzg3s-host: Move suspend/resume code into dedicated functions Claudiu Beznea
2026-10-02 11:17 ` sashiko-bot
2026-10-02 11:09 ` [PATCH v5 7/9] PCI: rzg3s-host: Move IRQ domain setup code Claudiu Beznea
2026-10-02 11:19 ` sashiko-bot
2026-10-02 11:09 ` [PATCH v5 8/9] PCI: rzg3s-host: Re-enumerate the bus on PCIe link-state changes Claudiu Beznea
2026-10-02 11:25 ` sashiko-bot
2026-10-05 13:50 ` Claudiu Beznea
2026-10-02 11:09 ` [PATCH v5 9/9] PCI: rzg3s-host: Add bridge::reset_root_port() Claudiu Beznea
2026-10-02 11:25 ` sashiko-bot
2026-10-05 14:55 ` Claudiu Beznea
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=f5144b5b-0890-4c19-9e0b-1c8a7b462233@kernel.org \
--to=claudiu.beznea@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.