From: Leon Romanovsky <leon@kernel.org>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com,
Chandramohan Akula <chandramohan.akula@broadcom.com>
Subject: Re: [PATCH for-next 1/3] RDMA/bnxt_re: Update HW interface headers
Date: Mon, 9 Oct 2023 09:09:15 +0300 [thread overview]
Message-ID: <20231009060915.GA5042@unreal> (raw)
In-Reply-To: <1696483889-17427-2-git-send-email-selvin.xavier@broadcom.com>
On Wed, Oct 04, 2023 at 10:31:27PM -0700, Selvin Xavier wrote:
> From: Chandramohan Akula <chandramohan.akula@broadcom.com>
>
> Updating the HW structures for the affiliated event and error
> reporting. Newly added interface structures will be used in the
> followup patch.
>
> Signed-off-by: Chandramohan Akula <chandramohan.akula@broadcom.com>
> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
> drivers/infiniband/hw/bnxt_re/roce_hsi.h | 62 ++++++++++++++++++++++++++++++++
> 1 file changed, 62 insertions(+)
<...>
> + #define CREQ_QP_ERROR_NOTIFICATION_REQ_ERR_STATE_REASON_LAST \
> + CREQ_QP_ERROR_NOTIFICATION_REQ_ERR_STATE_REASON_REQ_RETX_SETUP_ERROR
> __le32 xid;
<...>
> + #define CREQ_QP_ERROR_NOTIFICATION_RES_ERR_STATE_REASON_LAST \
> + CREQ_QP_ERROR_NOTIFICATION_RES_ERR_STATE_REASON_RES_PSN_NOT_FOUND
These defines are not used.
Thanks
> __le16 sq_cons_idx;
> __le16 rq_cons_idx;
> };
> --
> 2.5.5
>
next prev parent reply other threads:[~2023-10-09 6:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 5:31 [PATCH for-next 0/3] RDMA/bnxt_re: Async events update Selvin Xavier
2023-10-05 5:31 ` [PATCH for-next 1/3] RDMA/bnxt_re: Update HW interface headers Selvin Xavier
2023-10-09 6:09 ` Leon Romanovsky [this message]
2023-10-11 10:04 ` Selvin Xavier
2023-10-05 5:31 ` [PATCH for-next 2/3] RDMA/bnxt_re: Report async events and errors Selvin Xavier
2023-10-09 6:10 ` Leon Romanovsky
2023-10-11 10:04 ` Selvin Xavier
2023-10-05 5:31 ` [PATCH for-next 3/3] RDMA/bnxt_re: Do not report SRQ error in srq notification Selvin Xavier
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=20231009060915.GA5042@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=chandramohan.akula@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).