public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: "Håkon Bugge" <Haakon.Bugge@oracle.com>
Cc: Doug Ledford <dledford@redhat.com>,
	yishaih@mellanox.com, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, jgg@ziepe.ca,
	jackm@dev.mellanox.co.il
Subject: Re: [PATCH 1/2] IB/mlx4: Enable debug print of SMPs
Date: Mon, 17 Sep 2018 20:52:31 +0300	[thread overview]
Message-ID: <20180917175231.GO3661@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20180917145309.1255642-2-Haakon.Bugge@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 405 bytes --]

On Mon, Sep 17, 2018 at 04:53:08PM +0200, Håkon Bugge wrote:
> IB Subnet Management Packets (SMPs) were excluded from debug prints.
>
> Fixed by enabling print even on QP0 MADs.
>
> Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
> ---
>  drivers/infiniband/hw/mlx4/mad.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

Thanks,
Acked-by: Leon Romanovsky <leonro@mellanox.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2018-09-17 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 14:53 [PATCH 0/2] IB/mlx4: Enable debug print of SMPs and enhance output for MADs Håkon Bugge
2018-09-17 14:53 ` [PATCH 1/2] IB/mlx4: Enable debug print of SMPs Håkon Bugge
2018-09-17 17:52   ` Leon Romanovsky [this message]
2018-09-17 14:53 ` [PATCH 2/2] IB/mlx4: Add port and TID to MAD debug print Håkon Bugge
2018-09-17 16:05   ` kbuild test robot
2018-09-17 17:52   ` Leon Romanovsky
2018-09-17 20:15   ` kbuild test robot
  -- strict thread matches above, loose matches on Subject: below --
2018-09-17 17:56 [PATCH v2 0/2] IB/mlx4: Enable debug print of SMPs and enhance output for MADs Håkon Bugge
2018-09-17 17:56 ` [PATCH 1/2] IB/mlx4: Enable debug print of SMPs Håkon Bugge

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=20180917175231.GO3661@mtr-leonro.mtl.com \
    --to=leon@kernel.org \
    --cc=Haakon.Bugge@oracle.com \
    --cc=dledford@redhat.com \
    --cc=jackm@dev.mellanox.co.il \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yishaih@mellanox.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