From: Lukas Wunner <lukas@wunner.de>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Rafael J Wysocki <rafael@kernel.org>,
Guixin Liu <kanie@linux.alibaba.com>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH v13 2/5] PCI: Assume control of portdrv-related features only when portdrv enabled
Date: Sun, 20 Sep 2026 08:17:21 +0200 [thread overview]
Message-ID: <aq96cULSmdeBzd3D@wunner.de> (raw)
In-Reply-To: <20260919162655.3499010-3-sathyanarayanan.kuppuswamy@linux.intel.com>
On Sat, Sep 19, 2026 at 09:26:52AM -0700, Kuppuswamy Sathyanarayanan wrote:
> +++ b/drivers/pci/probe.c
> @@ -668,12 +668,14 @@ static void pci_init_host_bridge(struct pci_host_bridge *bridge)
> * may implement its own AER handling and use _OSC to prevent the
> * OS from interfering.
> */
> +#ifdef CONFIG_PCIEPORTBUS
> bridge->native_aer = 1;
> bridge->native_pcie_hotplug = 1;
> - bridge->native_shpc_hotplug = 1;
> bridge->native_pme = 1;
> - bridge->native_ltr = 1;
> bridge->native_dpc = 1;
> +#endif
> + bridge->native_ltr = 1;
> + bridge->native_shpc_hotplug = 1;
> bridge->domain_nr = PCI_DOMAIN_NR_NOT_SET;
How about (e.g.)
bridge->native_pcie_hotplug = IS_ENABLED(CONFIG_PCIEPORTBUS);
instead of using #ifdef? That's the preferred style according to
section 21 of Documentation/process/coding-style.rst
> bridge->native_cxl_error = 1;
Hm, this one depends on CONFIG_PCIEAER I believe.
(But Terry Bowman is the expert.)
Thanks,
Lukas
next prev parent reply other threads:[~2026-09-20 6:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 16:26 [PATCH v13 0/5] Simplify PCIe native ownership Kuppuswamy Sathyanarayanan
2026-09-19 16:26 ` [PATCH v13 1/5] PCI/DPC: Ignore devices with no AER Capability Kuppuswamy Sathyanarayanan
2026-09-19 16:35 ` sashiko-bot
2026-09-20 6:11 ` Lukas Wunner
2026-09-21 16:43 ` Kuppuswamy Sathyanarayanan
2026-09-21 19:01 ` Bjorn Helgaas
2026-09-19 16:26 ` [PATCH v13 2/5] PCI: Assume control of portdrv-related features only when portdrv enabled Kuppuswamy Sathyanarayanan
2026-09-19 16:33 ` sashiko-bot
2026-09-20 6:17 ` Lukas Wunner [this message]
2026-09-21 18:59 ` Kuppuswamy Sathyanarayanan
2026-09-21 19:01 ` Bjorn Helgaas
2026-09-22 17:30 ` Bowman, Terry
2026-09-19 16:26 ` [PATCH v13 3/5] PCI/ACPI: Tidy _OSC control bit checking Kuppuswamy Sathyanarayanan
2026-09-19 16:30 ` sashiko-bot
2026-09-22 13:18 ` Rafael J. Wysocki (Intel)
2026-09-19 16:26 ` [PATCH v13 4/5] PCI/ACPI: Centralize pcie_ports_native checking Kuppuswamy Sathyanarayanan
2026-09-19 16:39 ` sashiko-bot
2026-09-21 20:40 ` Kuppuswamy Sathyanarayanan
2026-09-20 7:24 ` Guixin Liu
2026-09-21 20:41 ` Kuppuswamy Sathyanarayanan
2026-09-22 13:16 ` Rafael J. Wysocki (Intel)
2026-09-19 16:26 ` [PATCH v13 5/5] PCI: Centralize pci_aer_available() checking Kuppuswamy Sathyanarayanan
2026-09-19 16:36 ` sashiko-bot
-- strict thread matches above, loose matches on Subject: below --
2021-01-23 1:11 [PATCH v13 0/5] Simplify PCIe native ownership Kuppuswamy Sathyanarayanan
2021-01-23 1:11 ` [PATCH v13 2/5] PCI: Assume control of portdrv-related features only when portdrv enabled Kuppuswamy Sathyanarayanan
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=aq96cULSmdeBzd3D@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=kanie@linux.alibaba.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rafael@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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.