All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederick Lawler <fred@fredlawl.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: mike.marciniszyn@intel.com, dennis.dalessandro@intel.com,
	linux-rdma@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 0/2] IB/hfi1: Cleanup PCIe link configuration
Date: Wed, 11 Apr 2018 23:32:56 -0500	[thread overview]
Message-ID: <5ACEE178.2010107@fredlawl.com> (raw)
In-Reply-To: <20180410182933.GC24642@bhelgaas-glaptop.roam.corp.google.com>

Bjorn Helgaas wrote:
> On Mon, Apr 09, 2018 at 06:22:46PM -0500, Frederick Lawler wrote:
>> Frederick Lawler wrote:
>>> The IB/hfi1 driver uses custom macros to configure link speed. Some macros were
>>> previously replaced, but not fully. This patch series addresses the 
>>> configuration inconsistencies and introduces minor cleanup by replacing
>>> redundant magic number usage.
> 
> Sorry for not responding to the actual patches; I'm not subscribed to
> linux-rdma, so reading them via an archive.
> 
>>> Frederick Lawler (2):
>>>   IB/hfi1: Replace custom hfi1 macros with PCIe macros
> 
> s/This patch removes/Remove/
> s/infavor/in favor/
> 
>> @@ -320,7 +315,7 @@ int pcie_speeds(struct hfi1_devdata *dd)
>> -	if ((linkcap & PCI_EXP_LNKCAP_SLS) != GEN3_SPEED_VECTOR) {
>> +	if ((linkcap & PCI_EXP_LNKCAP_SLS) != PCI_EXP_LNKSTA_CLS_8_0GB) {
> 
> Use PCI_EXP_LNKCAP_SLS_8_0GB (not PCI_EXP_LNKSTA_CLS_8_0GB) since
> we're testing a PCI_EXP_LNKCAP value.  They happen to be the same
> values, but we should use the matching definitions.
> 
>> @@ -1048,14 +1040,14 @@ int do_pcie_gen3_transition(struct hfi1_devdata *dd)
>> -		target_vector = GEN1_SPEED_VECTOR;
>> +		target_vector = PCI_EXP_LNKSTA_CLS_2_5GB;
> 
> target_vector is later ORed into a PCI_EXP_LNKCTL2 value.  We
> currently do not have any definitions for PCI_EXP_LNKCTL2.  We should
> add those, then use them here.  Similarly for the rest of this patch.
> 
>> -		target_speed = 8000;
>> +		target_speed = 8000;
> 
> Is there an unintended whitespace change here, e.g., trailing space or
> replacing tab with space?  I can't tell from the archive.
> 
>>>   IB/hfi1: Cleanup PCIe speed link configuration
> 
> s/speed link/link speed/

I'll add in the PCI_EXP_LINKCTL2_* macros into PCI and address the
remaining items.

Thanks for the feedback.

-- 
Frederick Lawler

      reply	other threads:[~2018-04-12  4:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1523244898-25942-1-git-send-email-fred@fredlawl.com>
2018-04-09 23:22 ` [PATCH v2 0/2] IB/hfi1: Cleanup PCIe link configuration Frederick Lawler
2018-04-10 18:29   ` Bjorn Helgaas
2018-04-12  4:32     ` Frederick Lawler [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=5ACEE178.2010107@fredlawl.com \
    --to=fred@fredlawl.com \
    --cc=dennis.dalessandro@intel.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mike.marciniszyn@intel.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.