From: Leon Romanovsky <leon@kernel.org>
To: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com, selvin.xavier@broadcom.com,
Preethi G <preethi.gurusiddalingeswaraswamy@broadcom.com>
Subject: Re: [PATCH for-rc 5/5] RDMA/bnxt_re: Fix reporting hw_ver in query_device
Date: Mon, 16 Dec 2024 15:32:04 +0200 [thread overview]
Message-ID: <20241216133204.GJ1245331@unreal> (raw)
In-Reply-To: <20241211083931.968831-6-kalesh-anakkur.purayil@broadcom.com>
On Wed, Dec 11, 2024 at 02:09:31PM +0530, Kalesh AP wrote:
> Driver currently populates subsystem_device id in the
> "hw_ver" field of ib_attr structure in query_device.
I applied this patch, but it is not currently, it was the case for last
7 years and it has chances to break your customers.
Thanks
>
> Updated to populate PCI revision ID.
>
> Fixes: 1ac5a4047975 ("RDMA/bnxt_re: Add bnxt_re RoCE driver")
> Reviewed-by: Preethi G <preethi.gurusiddalingeswaraswamy@broadcom.com>
> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
> drivers/infiniband/hw/bnxt_re/ib_verbs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/bnxt_re/ib_verbs.c b/drivers/infiniband/hw/bnxt_re/ib_verbs.c
> index bcb7cfc63d09..e3d26bd6de05 100644
> --- a/drivers/infiniband/hw/bnxt_re/ib_verbs.c
> +++ b/drivers/infiniband/hw/bnxt_re/ib_verbs.c
> @@ -199,7 +199,7 @@ int bnxt_re_query_device(struct ib_device *ibdev,
>
> ib_attr->vendor_id = rdev->en_dev->pdev->vendor;
> ib_attr->vendor_part_id = rdev->en_dev->pdev->device;
> - ib_attr->hw_ver = rdev->en_dev->pdev->subsystem_device;
> + ib_attr->hw_ver = rdev->en_dev->pdev->revision;
> ib_attr->max_qp = dev_attr->max_qp;
> ib_attr->max_qp_wr = dev_attr->max_qp_wqes;
> ib_attr->device_cap_flags =
> --
> 2.43.5
>
next prev parent reply other threads:[~2024-12-16 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 8:39 [PATCH for-rc 0/5] bnxt_re Bug fixes Kalesh AP
2024-12-11 8:39 ` [PATCH for-rc 1/5] RDMA/bnxt_re: Fix the check for 9060 condition Kalesh AP
2024-12-11 8:39 ` [PATCH for-rc 2/5] RDMA/bnxt_re: Add check for path mtu in modify_qp Kalesh AP
2024-12-11 8:39 ` [PATCH for-rc 3/5] RDMA/bnxt_re: Fix setting mandatory attributes for modify_qp Kalesh AP
2024-12-11 8:39 ` [PATCH for-rc 4/5] RDMA/bnxt_re: Fix to export port num to ib_query_qp Kalesh AP
2024-12-11 8:39 ` [PATCH for-rc 5/5] RDMA/bnxt_re: Fix reporting hw_ver in query_device Kalesh AP
2024-12-16 13:32 ` Leon Romanovsky [this message]
2024-12-16 13:34 ` [PATCH for-rc 0/5] bnxt_re Bug fixes Leon Romanovsky
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=20241216133204.GJ1245331@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=linux-rdma@vger.kernel.org \
--cc=preethi.gurusiddalingeswaraswamy@broadcom.com \
--cc=selvin.xavier@broadcom.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