This workaround presented in 58d74bb is not something we should alert the user
on. Debug level message is enough.
Signed-off-by: Eli Cohen <e...@mellanox.co.il>
---
drivers/net/mlx4/fw.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/mlx4/fw.c b/drivers/net/mlx4/fw.c
index 7a7e18b..9f415df 100644
--- a/drivers/net/mlx4/fw.c
+++ b/drivers/net/mlx4/fw.c
@@ -290,7 +290,7 @@ int mlx4_QUERY_DEV_CAP(struct mlx4_dev *dev, struct
mlx4_dev_cap *dev_cap)
dev_cap->bf_reg_size = 1 << (field & 0x1f);
MLX4_GET(field, outbox,
QUERY_DEV_CAP_LOG_MAX_BF_REGS_PER_PAGE_OFFSET);
if ((1 << (field & 0x3f)) > (PAGE_SIZE / dev_cap->bf_reg_size))
{
- mlx4_warn(dev, "firmware bug: log2 # of blue flame regs
is invalid (%d), forcing 3\n", field & 0x1f);
+ mlx4_dbg(dev, "firmware bug: log2 # of blue flame regs
is invalid (%d), forcing 3\n", field & 0x1f);
field = 3;
}
dev_cap->bf_regs_per_page = 1 << (field & 0x3f);
--
1.7.3.2
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
