[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 10 Oct 2019 11:14:17 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: linux-pci@...r.kernel.org,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Sagi Grimberg <sagi@...mberg.me>,
Mario Limonciello <Mario.Limonciello@...l.com>,
Keith Busch <keith.busch@...el.com>,
Kai-Heng Feng <kai.heng.feng@...onical.com>,
Rajat Jain <rajatja@...gle.com>,
Heiner Kallweit <hkallweit1@...il.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org
Subject: Re: [PATCH 1/1] PCI/ASPM: Remove pcie_aspm_enabled() unnecessary
locking
On Thu, Oct 10, 2019 at 04:01:21PM +0200, Christoph Hellwig wrote:
> On Thu, Oct 10, 2019 at 07:47:46AM -0500, Bjorn Helgaas wrote:
> > + return bridge->link_state ? !!bridge->link_state->aspm_enabled : false;
>
> Can we unobsfucated this while we're at it?
>
> if (!bridge->link_state)
> return false;
> return bridge->link_state->aspm_enabled;
Yep, after some of the follow-up patches from Heiner, it looks like
this:
bool pcie_aspm_enabled(struct pci_dev *pdev)
{
struct pcie_link_state *link = pcie_aspm_get_link(pdev);
if (!link)
return false;
return link->aspm_enabled;
}
Powered by blists - more mailing lists