From: "Saheed O. Bolarinwa" <refactormyself@gmail.com>
To: helgaas@kernel.org
Cc: "Bolarinwa O. Saheed" <refactormyself@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH v1 0/4] Remove struct pcie_link_state.clkpm_*
Date: Wed, 29 Sep 2021 02:43:56 +0200 [thread overview]
Message-ID: <20210929004400.25717-1-refactormyself@gmail.com> (raw)
From: "Bolarinwa O. Saheed" <refactormyself@gmail.com>
These series removes the Clock PM members of the
struct pcie_link_state. Another member is introduced to mark
devices that the kernel has disbled.
MERGE NOTICE:
These series are based on
» 'commit e4e737bb5c17 ("Linux 5.15-rc2")'
Bolarinwa O. Saheed (4):
[PCI/ASPM:] Remove struct pcie_link_state.clkpm_default
PCI/ASPM: Remove struct pcie_link_state.clkpm_capable
PCI/ASPM: Remove struct pcie_link_state.clkpm_enabled
PCI/ASPM: Remove struct pcie_link_state.clkpm_disable
drivers/pci/pcie/aspm.c | 95 +++++++++++++++++++++++------------------
1 file changed, 53 insertions(+), 42 deletions(-)
--
2.20.1
next reply other threads:[~2021-09-29 0:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 0:43 Saheed O. Bolarinwa [this message]
2021-09-29 0:43 ` [RFC PATCH v1 1/4] [PCI/ASPM:] Remove struct pcie_link_state.clkpm_default Saheed O. Bolarinwa
2021-09-30 15:54 ` Bjorn Helgaas
2021-10-11 6:05 ` Saheed Bolarinwa
2021-09-29 0:43 ` [RFC PATCH v1 2/4] PCI/ASPM: Remove struct pcie_link_state.clkpm_capable Saheed O. Bolarinwa
2021-09-30 16:05 ` Bjorn Helgaas
2021-09-29 0:43 ` [RFC PATCH v1 3/4] PCI/ASPM: Remove struct pcie_link_state.clkpm_enabled Saheed O. Bolarinwa
2021-09-30 16:28 ` Bjorn Helgaas
2021-09-29 0:44 ` [RFC PATCH v1 4/4] PCI/ASPM: Remove struct pcie_link_state.clkpm_disable Saheed O. Bolarinwa
2021-09-30 20:20 ` Bjorn Helgaas
2021-10-11 6:06 ` Saheed Bolarinwa
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=20210929004400.25717-1-refactormyself@gmail.com \
--to=refactormyself@gmail.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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).