From: Sinan Kaya <okaya@kernel.org>
To: Yicong Yang <yangyicong@hisilicon.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH] PCI/ASPM: Print correct ASPM status when _OSC failed
Date: Tue, 2 Jun 2020 13:50:37 -0400 [thread overview]
Message-ID: <dd5ba708-18a9-fd42-8cf1-af32ef367d5e@kernel.org> (raw)
In-Reply-To: <60d31995-1511-4d82-b026-e7119d88a891@hisilicon.com>
Bjorn,
On 6/1/2020 9:57 PM, Yicong Yang wrote:
> well, Sinan's words make sense to me. But I'm still confused that, the message
> says we're "disabling ASPM" but ASPM maybe enabled if we designate
> pcie_aspm=force as I mentioned in the commit message. Will it be possible if
> we replace "disabling" to "disabled" or we can do something else to make
> the message reflect the real status of ASPM?
What do you think?
Sinan
next prev parent reply other threads:[~2020-06-02 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 8:38 [PATCH] PCI/ASPM: Print correct ASPM status when _OSC failed Yicong Yang
2020-05-28 11:42 ` Rafael J. Wysocki
2020-06-01 15:14 ` Sinan Kaya
2020-06-01 15:22 ` Rafael J. Wysocki
2020-06-02 1:57 ` Yicong Yang
2020-06-02 17:50 ` Sinan Kaya [this message]
2020-06-02 22:36 ` Bjorn Helgaas
2020-06-02 23:21 ` Sean V Kelley
2020-06-03 4:48 ` Sinan Kaya
[not found] ` <03d2a6ca-78de-2d39-5428-2949c2017099@hisilicon.com>
2020-06-03 13:02 ` [PATCH v2] ACPI: PCI: Remove ASPM text from _OSC failure message Rafael J. Wysocki
2020-06-03 13:19 ` Yicong Yang
2020-06-03 12:59 ` [PATCH] PCI/ASPM: Print correct ASPM status when _OSC failed Rafael J. Wysocki
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=dd5ba708-18a9-fd42-8cf1-af32ef367d5e@kernel.org \
--to=okaya@kernel.org \
--cc=helgaas@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=yangyicong@hisilicon.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;
as well as URLs for NNTP newsgroup(s).