2018-01-04 21:04:20

by Jonathan Toppins

[permalink] [raw]
Subject: [rdma for-next] bnxt_re: report RoCE device support at info level

Reporting that a device doesn't support RoCE seems like a valuable piece
of information to have when trying to determine why a driver is not binding
to a device. Better to report this at info log level instead of requiring
a user to enable all debug messages in the driver.

Signed-off-by: Jonathan Toppins <[email protected]>
---
drivers/infiniband/hw/bnxt_re/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/infiniband/hw/bnxt_re/main.c b/drivers/infiniband/hw/bnxt_re/main.c
index aafc19aa5de1..bf268bf1f496 100644
--- a/drivers/infiniband/hw/bnxt_re/main.c
+++ b/drivers/infiniband/hw/bnxt_re/main.c
@@ -417,7 +417,7 @@ static struct bnxt_en_dev *bnxt_re_dev_probe(struct net_device *netdev)
return ERR_PTR(-EINVAL);

if (!(en_dev->flags & BNXT_EN_FLAG_ROCE_CAP)) {
- dev_dbg(&pdev->dev,
+ dev_info(&pdev->dev,
"%s: probe error: RoCE is not supported on this device",
ROCE_DRV_MODULE_NAME);
return ERR_PTR(-ENODEV);
--
2.13.6


2018-01-05 09:52:46

by Devesh Sharma

[permalink] [raw]
Subject: Re: [rdma for-next] bnxt_re: report RoCE device support at info level

Acked-By: Devesh Sharma <[email protected]>

On Fri, Jan 5, 2018 at 2:34 AM, Jonathan Toppins <[email protected]> wrote:
> Reporting that a device doesn't support RoCE seems like a valuable piece
> of information to have when trying to determine why a driver is not binding
> to a device. Better to report this at info log level instead of requiring
> a user to enable all debug messages in the driver.
>
> Signed-off-by: Jonathan Toppins <[email protected]>
> ---
> drivers/infiniband/hw/bnxt_re/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/bnxt_re/main.c b/drivers/infiniband/hw/bnxt_re/main.c
> index aafc19aa5de1..bf268bf1f496 100644
> --- a/drivers/infiniband/hw/bnxt_re/main.c
> +++ b/drivers/infiniband/hw/bnxt_re/main.c
> @@ -417,7 +417,7 @@ static struct bnxt_en_dev *bnxt_re_dev_probe(struct net_device *netdev)
> return ERR_PTR(-EINVAL);
>
> if (!(en_dev->flags & BNXT_EN_FLAG_ROCE_CAP)) {
> - dev_dbg(&pdev->dev,
> + dev_info(&pdev->dev,
> "%s: probe error: RoCE is not supported on this device",
> ROCE_DRV_MODULE_NAME);
> return ERR_PTR(-ENODEV);
> --
> 2.13.6
>

2018-01-05 19:34:53

by Doug Ledford

[permalink] [raw]
Subject: Re: [rdma for-next] bnxt_re: report RoCE device support at info level

On Fri, 2018-01-05 at 15:22 +0530, Devesh Sharma wrote:
> Acked-By: Devesh Sharma <[email protected]>
>
> On Fri, Jan 5, 2018 at 2:34 AM, Jonathan Toppins <[email protected]> wrote:
> > Reporting that a device doesn't support RoCE seems like a valuable piece
> > of information to have when trying to determine why a driver is not binding
> > to a device. Better to report this at info log level instead of requiring
> > a user to enable all debug messages in the driver.
> >
> > Signed-off-by: Jonathan Toppins <[email protected]>

Applied, thanks.

--
Doug Ledford <[email protected]>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD


Attachments:
signature.asc (833.00 B)
This is a digitally signed message part