From: David Miller <davem@davemloft.net>
To: helgaas@kernel.org
Cc: netdev@vger.kernel.org, linux-pci@vger.kernel.org,
Ariel.Elior@cavium.com, everest-linux-l2@cavium.com
Subject: Re: [PATCH] qed: Remove unused QED_RDMA_DEV_CAP_* symbols and dev->dev_caps
Date: Mon, 18 Dec 2017 15:25:49 -0500 (EST) [thread overview]
Message-ID: <20171218.152549.561346578863404231.davem@davemloft.net> (raw)
In-Reply-To: <20171218.151354.978438255508508144.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Mon, 18 Dec 2017 15:13:54 -0500 (EST)
> From: Bjorn Helgaas <helgaas@kernel.org>
> Date: Fri, 15 Dec 2017 17:03:01 -0600
>
>> From: Bjorn Helgaas <bhelgaas@google.com>
>>
>> The QED_RDMA_DEV_CAP_* symbols are only used to set bits in dev->dev_caps.
>> Nobody ever looks at those bits. Remove the symbols and dev_caps itself.
>>
>> Note that if these are ever used and added back, it looks incorrect to set
>> QED_RDMA_DEV_CAP_ATOMIC_OP based on PCI_EXP_DEVCTL2_LTR_EN. LTR is the
>> Latency Tolerance Reporting mechanism, which has nothing to do with Atomic
>> Ops.
>>
>> No functional change intended.
>>
>> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
>
> Applied to net-next.
Actually, this doesn't build, reverted:
drivers/infiniband/hw/qedr/main.c: In function ‘qedr_set_device_attr’:
drivers/infiniband/hw/qedr/main.c:682:27: error: ‘struct qed_rdma_device’ has no member named ‘dev_caps’
attr->dev_caps = qed_attr->dev_caps;
prev parent reply other threads:[~2017-12-18 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 23:03 [PATCH] qed: Remove unused QED_RDMA_DEV_CAP_* symbols and dev->dev_caps Bjorn Helgaas
2017-12-18 13:30 ` Amrani, Ram
2017-12-18 20:13 ` David Miller
2017-12-18 20:25 ` David Miller [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=20171218.152549.561346578863404231.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ariel.Elior@cavium.com \
--cc=everest-linux-l2@cavium.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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