All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Vidya Sagar <sagar.tv@gmail.com>
Cc: bhelgaas@google.com, rjw@rjwysocki.net, nchumbalkar@lenovo.com,
	swarren@nvidia.com, kthota@nvidia.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, vidyas@nvidia.com
Subject: Re: [PATCH v2] PCI: enable ASPM configuration in PCIE POWERSAVE mode
Date: Wed, 16 Jul 2014 10:15:37 +0200	[thread overview]
Message-ID: <20140716081533.GJ7978@ulmo> (raw)
In-Reply-To: <1405317877-15060-1-git-send-email-vidyas@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

On Mon, Jul 14, 2014 at 11:34:37AM +0530, Vidya Sagar wrote:
> From: Vidya Sagar <sagar.tv@gmail.com>

The commit message looks somewhat cluttered:

> 'commit 1a680b7c3258 ("PCI: PCIe links may not get configured for ASPM
>  under POWERSAVE mode")'

Usually you'd cite a commit without the extra single quotes. More like
this:

Commit 1a680b7c3258 ("PCI: PCIe links may not get configured for ASPM
under POWERSAVE mode") moved...

> moved pcie_aspm_powersave_config_link() out of
> pci_raw_set_power_state() to pci_set_power_state() which would enable
> ASPM. But, with 'commit db288c9c5f9d ("PCI / PM: restore the original
>  behavior of pci_set_power_state()")',

Same here.

>                                        which re-introduced the following check
> ./drivers/pci/pci.c: pci_set_power_state()
> +   /* Check if we're already there */
> +   if (dev->current_state == state)
> +       return 0;

To make this stand out better, it could be preceded and followed by a
single blank line (and perhaps indented using tabs).

> in pci_set_power_state(), call to pcie_aspm_powersave_config_link() is never
> made leaving ASPM broken.
> Fix it by not returning from when the above condition is true, rather, jump to
> ASPM configuration code and exit from there eventually.
> 
> Signed-off-by: Vidya Sagar <sagar.tv@gmail.com>

This patch uses code suggested by Bjorn and it's customary to credit the
original author using something like:

	Suggested-by: Bjorn Helgaas <bhelgaas@google.com>

or

	Originally-by: Bjorn Helgaas <bhelgaas@google.com>

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2014-07-16  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14  6:04 [PATCH v2] PCI: enable ASPM configuration in PCIE POWERSAVE mode Vidya Sagar
2014-07-15 20:51 ` Bjorn Helgaas
2014-07-16  8:15 ` Thierry Reding [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=20140716081533.GJ7978@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=kthota@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nchumbalkar@lenovo.com \
    --cc=rjw@rjwysocki.net \
    --cc=sagar.tv@gmail.com \
    --cc=swarren@nvidia.com \
    --cc=vidyas@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.