From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: <sagi@grimberg.me>, <leonro@nvidia.com>,
<linux-rdma@vger.kernel.org>, <jgg@nvidia.com>
Cc: <israelr@nvidia.com>, <oren@nvidia.com>, <sergeygo@nvidia.com>,
"Max Gurtovoy" <mgurtovoy@nvidia.com>
Subject: [PATCH 1/3] IB/iser: remove unused macros
Date: Thu, 30 Mar 2023 16:13:31 +0300 [thread overview]
Message-ID: <20230330131333.37900-1-mgurtovoy@nvidia.com> (raw)
The removed macros are old leftovers.
Reviewed-by: Sergey Gorenko <sergeygo@nvidia.com>
Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
---
drivers/infiniband/ulp/iser/iser_verbs.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/drivers/infiniband/ulp/iser/iser_verbs.c b/drivers/infiniband/ulp/iser/iser_verbs.c
index 1b8eda0dae4e..95b8eebf7e04 100644
--- a/drivers/infiniband/ulp/iser/iser_verbs.c
+++ b/drivers/infiniband/ulp/iser/iser_verbs.c
@@ -37,12 +37,6 @@
#include "iscsi_iser.h"
-#define ISCSI_ISER_MAX_CONN 8
-#define ISER_MAX_RX_LEN (ISER_QP_MAX_RECV_DTOS * ISCSI_ISER_MAX_CONN)
-#define ISER_MAX_TX_LEN (ISER_QP_MAX_REQ_DTOS * ISCSI_ISER_MAX_CONN)
-#define ISER_MAX_CQ_LEN (ISER_MAX_RX_LEN + ISER_MAX_TX_LEN + \
- ISCSI_ISER_MAX_CONN)
-
static void iser_qp_event_callback(struct ib_event *cause, void *context)
{
iser_err("qp event %s (%d)\n",
--
2.18.1
next reply other threads:[~2023-03-30 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 13:13 Max Gurtovoy [this message]
2023-03-30 13:13 ` [PATCH 2/3] IB/iser: centralize setting desc type and done callback Max Gurtovoy
2023-03-30 13:51 ` Sagi Grimberg
2023-03-30 13:13 ` [PATCH 3/3] IB/iser: remove redundant new line Max Gurtovoy
2023-03-30 13:52 ` Sagi Grimberg
2023-03-30 13:51 ` [PATCH 1/3] IB/iser: remove unused macros Sagi Grimberg
2023-04-03 12:40 ` 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=20230330131333.37900-1-mgurtovoy@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=israelr@nvidia.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=oren@nvidia.com \
--cc=sagi@grimberg.me \
--cc=sergeygo@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 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).