[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240109083253.3629967-2-lizhijian@fujitsu.com>
Date: Tue, 9 Jan 2024 16:32:53 +0800
From: Li Zhijian <lizhijian@...itsu.com>
To: linux-rdma@...r.kernel.org
Cc: zyjzyj2000@...il.com,
jgg@...pe.ca,
leon@...nel.org,
linux-kernel@...r.kernel.org,
rpearsonhpe@...il.com,
Li Zhijian <lizhijian@...itsu.com>
Subject: [PATCH for-next v4 2/2] RDMA/rxe: Remove rxe_info from rxe_set_mtu
commit 9ac01f434a1e ("RDMA/rxe: Extend dbg log messages to err and info")
newly added this info. But it did only show null device when
the rdma_rxe is being loaded because dev_name(rxe->ib_dev->dev)
has not yet been assigned at the moment:
"(null): rxe_set_mtu: Set mtu to 1024"
Remove it to silent this message, check the mtu from it backend link
instead if needed.
CC: Bob Pearson <rpearsonhpe@...il.com>
Signed-off-by: Li Zhijian <lizhijian@...itsu.com>
---
V4: Remove it rather than re-order rxe_set_mtu() and rxe_register_device()
---
drivers/infiniband/sw/rxe/rxe.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/infiniband/sw/rxe/rxe.c b/drivers/infiniband/sw/rxe/rxe.c
index a086d588e159..ae466e72fc43 100644
--- a/drivers/infiniband/sw/rxe/rxe.c
+++ b/drivers/infiniband/sw/rxe/rxe.c
@@ -160,8 +160,6 @@ void rxe_set_mtu(struct rxe_dev *rxe, unsigned int ndev_mtu)
port->attr.active_mtu = mtu;
port->mtu_cap = ib_mtu_enum_to_int(mtu);
-
- rxe_info_dev(rxe, "Set mtu to %d\n", port->mtu_cap);
}
/* called by ifc layer to create new rxe device.
--
2.29.2
Powered by blists - more mailing lists