From: Jeff Johnson <jjohnson@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>,
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>
Cc: 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 0/4] PCI/arm64/ath11k/ath12k: Rename pwrctrl Kconfig symbols
Date: Fri, 28 Mar 2025 09:11:29 -0700 [thread overview]
Message-ID: <04201b5a-34fe-45e0-bb96-237bd6eec414@kernel.org> (raw)
In-Reply-To: <20250328143646.27678-1-johan+linaro@kernel.org>
On 3/28/2025 7:36 AM, Johan Hovold wrote:
> The PCI pwrctrl framework was renamed after being merged, but the
> Kconfig symbols still reflect the old name ("pwrctl" without an "r").
>
> This leads to people not knowing how to refer to the framework in
> writing, inconsistencies in module naming, etc.
>
> Let's rename also the Kconfig symbols before this gets any worse.
>
> The arm64, ath11k and ath12k changes could go through the corresponding
> subsystem trees once they have the new symbols (e.g. in the next cycle)
> or they could all go in via the PCI tree with an ack from their
> maintainers.
I'm fine with the entire series going through PCI
Acked-by: Jeff Johnson <jjohnson@kernel.org> # drivers/net/wireless/ath/...
>
> There are some new pwrctrl drivers and an arm64 defconfig change on the
> lists so we may need to keep deprecated symbols for a release or two.
>
> Johan
>
>
> Johan Hovold (4):
> PCI/pwrctrl: Rename pwrctrl Kconfig symbols and slot module
> arm64: Kconfig: switch to HAVE_PWRCTRL
> wifi: ath11k: switch to PCI_PWRCTRL_PWRSEQ
> wifi: ath12k: switch to PCI_PWRCTRL_PWRSEQ
>
> arch/arm64/Kconfig.platforms | 2 +-
> drivers/net/wireless/ath/ath11k/Kconfig | 2 +-
> drivers/net/wireless/ath/ath12k/Kconfig | 2 +-
> drivers/pci/pwrctrl/Kconfig | 27 +++++++++++++++++++------
> drivers/pci/pwrctrl/Makefile | 8 ++++----
> 5 files changed, 28 insertions(+), 13 deletions(-)
>
next prev parent reply other threads:[~2025-03-28 16:11 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
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 ` Jeff Johnson [this message]
2025-04-02 8:00 ` [PATCH 0/4] PCI/arm64/ath11k/ath12k: Rename pwrctrl Kconfig symbols 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=04201b5a-34fe-45e0-bb96-237bd6eec414@kernel.org \
--to=jjohnson@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=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 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.