From: Vidya Sagar <vidyas@nvidia.com>
To: Bjorn Helgaas <helgaas@kernel.org>, <linux-pci@vger.kernel.org>
Cc: Rajat Jain <rajatja@google.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/4] PCI/ASPM: Fix some L1 substate configuration
Date: Tue, 14 Nov 2017 18:53:19 +0530 [thread overview]
Message-ID: <01b3d7b6-9d0e-e442-87d4-32aa6728fbd8@nvidia.com> (raw)
In-Reply-To: <20171113230937.4120.68038.stgit@bhelgaas-glaptop.roam.corp.google.com>
On Tuesday 14 November 2017 04:41 AM, Bjorn Helgaas wrote:
> The first two patches fix typos that cause incorrect L1 substate
> configuration. The last two are cosmetic for maintainability.
>
> These are minor enough that I'd like to squeeze them into v4.15 unless
> anybody objects.
>
> ---
>
> Bjorn Helgaas (4):
> PCI/ASPM: Account for downstream device's Port Common_Mode_Restore_Time
> PCI/ASPM: Use correct capability pointer to program LTR_L1.2_THRESHOLD
> PCI/ASPM: Reformat ASPM register definitions
> PCI/ASPM: Add L1 Substates definitions
>
>
> drivers/pci/pcie/aspm.c | 38 ++++++++++++++++++++++----------------
> include/uapi/linux/pci_regs.h | 34 ++++++++++++++++++++--------------
> 2 files changed, 42 insertions(+), 30 deletions(-)
Reviewed-by: Vidya Sagar <vidyas@nvidia.com>
prev parent reply other threads:[~2017-11-14 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 23:11 Bjorn Helgaas
2017-11-13 23:11 ` [PATCH v1 1/4] PCI/ASPM: Account for downstream device's Port Common_Mode_Restore_Time Bjorn Helgaas
2017-11-13 23:12 ` [PATCH v1 2/4] PCI/ASPM: Use correct capability pointer to program LTR_L1.2_THRESHOLD Bjorn Helgaas
2017-11-13 23:12 ` [PATCH v1 3/4] PCI/ASPM: Reformat ASPM register definitions Bjorn Helgaas
2017-11-13 23:12 ` [PATCH v1 4/4] PCI/ASPM: Add L1 Substates definitions Bjorn Helgaas
2017-11-14 13:23 ` Vidya Sagar [this message]
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=01b3d7b6-9d0e-e442-87d4-32aa6728fbd8@nvidia.com \
--to=vidyas@nvidia.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rajatja@google.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®