From: Kenneth Crudup <kenny@panix.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>
Cc: "David E. Box" <david.e.box@linux.intel.com>,
rafael@kernel.org, bhelgaas@google.com,
vicamo.yang@canonical.com, ilpo.jarvinen@linux.intel.com,
nirmal.patel@linux.intel.com, linux-pm@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Kenneth C <kenny@panix.com>
Subject: Re: [PATCH V3 1/2] PCI/ASPM: Add host-bridge API to override default ASPM/CLKPM link state
Date: Thu, 4 Sep 2025 10:16:55 -0700 [thread overview]
Message-ID: <121a26de-b5d4-42a2-ae52-02b386f17109@panix.com> (raw)
In-Reply-To: <20250904171158.GA1268495@bhelgaas>
On 9/4/25 10:11, Bjorn Helgaas wrote:
> but if we can get in -next for a bit now, that would be great.
Yes, please 🙂 Other than some my-hardware-specific gcc flags, this
effort in its various forms is the only diff between Linus' master and
what I run, and for nearly 3 years now; it'd be great to see it in
mainline (and a hearty thank you all for getting us nearly there!)
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
next prev parent reply other threads:[~2025-09-04 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 20:35 David E. Box
2025-08-25 20:35 ` [PATCH V3 2/2] PCI: vmd: Use pci_host_set_default_pcie_link_state() to set ASPM defaults David E. Box
2025-08-28 20:43 ` [PATCH V3 1/2] PCI/ASPM: Add host-bridge API to override default ASPM/CLKPM link state Bjorn Helgaas
2025-08-29 19:54 ` David Box
2025-09-03 23:04 ` Bjorn Helgaas
2025-09-04 16:02 ` David Box
2025-09-04 16:35 ` Manivannan Sadhasivam
2025-08-31 12:58 ` Manivannan Sadhasivam
2025-09-03 22:55 ` Bjorn Helgaas
2025-09-04 16:45 ` Manivannan Sadhasivam
2025-09-04 17:11 ` Bjorn Helgaas
2025-09-04 17:16 ` Kenneth Crudup [this message]
2025-09-24 6:12 ` Manivannan Sadhasivam
2025-10-06 19:42 ` Kenneth Crudup
2025-09-04 21:11 ` Kenneth Crudup
2025-09-22 18:38 ` Kenneth Crudup
2025-09-04 21:12 ` Kenneth Crudup
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=121a26de-b5d4-42a2-ae52-02b386f17109@panix.com \
--to=kenny@panix.com \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mani@kernel.org \
--cc=nirmal.patel@linux.intel.com \
--cc=rafael@kernel.org \
--cc=vicamo.yang@canonical.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 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®