From: LECOINTRE Philippe <philippe.lecointre@thalesgroup.com>
To: "jingoohan1@gmail.com" <jingoohan1@gmail.com>,
"mani@kernel.org" <mani@kernel.org>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"kwilczynski@kernel.org" <kwilczynski@kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>
Subject: [PATCH] PCI: dwc: Correct PCIE_DW_PLAT_EP reference in Kconfig help
Date: Fri, 2 Oct 2026 08:07:07 +0000 [thread overview]
Message-ID: <305ef70ecadb4db9aa42c66607240aba@thalesgroup.com> (raw)
The Kconfig help text for PCIE_DW_PLAT_HOST and PCIE_DW_PLAT_EP
incorrectly refers to PCI_DW_PLAT_EP.
Replace the typo with the correct symbol name, PCIE_DW_PLAT_EP, so the
help text matches the actual Kconfig option.
Signed-off-by: Philippe Lecointre <philippe.lecointre@thalesgroup.com>
---
drivers/pci/controller/dwc/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/controller/dwc/Kconfig b/drivers/pci/controller/dwc/Kconfig
index dcfbe7e229fd..0a0d56fcf0ac 100644
--- a/drivers/pci/controller/dwc/Kconfig
+++ b/drivers/pci/controller/dwc/Kconfig
@@ -295,7 +295,7 @@ config PCIE_DW_PLAT_HOST
Designware IP.
This controller can work either as EP or RC. In order to enable
host-specific features PCIE_DW_PLAT_HOST must be selected and in
- order to enable device-specific features PCI_DW_PLAT_EP must be
+ order to enable device-specific features PCIE_DW_PLAT_EP must be
selected.
config PCIE_DW_PLAT_EP
@@ -310,7 +310,7 @@ config PCIE_DW_PLAT_EP
in Designware IP.
This controller can work either as EP or RC. In order to enable
host-specific features PCIE_DW_PLAT_HOST must be selected and in
- order to enable device-specific features PCI_DW_PLAT_EP must be
+ order to enable device-specific features PCIE_DW_PLAT_EP must be
selected.
config PCIE_QCOM_COMMON
--
2.27.0
reply other threads:[~2026-10-02 8:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=305ef70ecadb4db9aa42c66607240aba@thalesgroup.com \
--to=philippe.lecointre@thalesgroup.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®