From: Bjorn Helgaas <helgaas@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jeff Johnson <jjohnson@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
ath11k@lists.infradead.org, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] PCI/pwrctrl: Rename pwrctrl Kconfig symbols and slot module
Date: Fri, 28 Mar 2025 10:13:43 -0500 [thread overview]
Message-ID: <20250328151343.GA1505019@bhelgaas> (raw)
In-Reply-To: <20250328143646.27678-2-johan+linaro@kernel.org>
On Fri, Mar 28, 2025 at 03:36:43PM +0100, Johan Hovold wrote:
> Commits b88cbaaa6fa1 ("PCI/pwrctrl: Rename pwrctl files to pwrctrl") and
> 3f925cd62874 ("PCI/pwrctrl: Rename pwrctrl functions and structures")
> renamed the "pwrctl" framework to "pwrctrl" for consistency reasons.
>
> Rename also the Kconfig symbols so that they reflect the new name while
> adding entries for the deprecated ones. The old symbols can be removed
> once everything that depends on them has been updated.
I considered changing the Kconfig symbols at the time, but didn't do
it because I didn't want to break existing .config files. Is that not
a concern? Or do you think the long-term benefit is worth having
users re-answer these config questions?
We have lots of Kconfig symbols that are not what we would choose
today, e.g., my misguided suggestion years ago to use "CONFIG_PCI_*"
instead of "CONFIG_PCIE_*" for PCIe controller drivers that didn't
have any PCIe content.
If we do want this, I would think we should squash all these so we
don't have breakage between this patch and the following ones.
Bjorn
next prev parent reply other threads:[~2025-03-28 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 14:36 [PATCH 0/4] PCI/arm64/ath11k/ath12k: Rename pwrctrl Kconfig symbols Johan Hovold
2025-03-28 14:36 ` [PATCH 1/4] PCI/pwrctrl: Rename pwrctrl Kconfig symbols and slot module Johan Hovold
2025-03-28 15:13 ` Bjorn Helgaas [this message]
2025-03-28 15:50 ` Johan Hovold
2025-04-02 11:54 ` Jonas Gorski
2025-04-02 12:38 ` Johan Hovold
2025-03-28 14:36 ` [PATCH 2/4] arm64: Kconfig: switch to HAVE_PWRCTRL Johan Hovold
2025-03-28 14:36 ` [PATCH 3/4] wifi: ath11k: switch to PCI_PWRCTRL_PWRSEQ Johan Hovold
2025-03-28 14:36 ` [PATCH 4/4] wifi: ath12k: " Johan Hovold
2025-03-28 16:11 ` [PATCH 0/4] PCI/arm64/ath11k/ath12k: Rename pwrctrl Kconfig symbols Jeff Johnson
2025-04-02 8:00 ` Manivannan Sadhasivam
2025-04-02 8:13 ` Bartosz Golaszewski
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=20250328151343.GA1505019@bhelgaas \
--to=helgaas@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=catalin.marinas@arm.com \
--cc=jjohnson@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=will@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).