From: Doug Ledford <dledford@redhat.com>
To: "Håkon Bugge" <Haakon.Bugge@oracle.com>,
"Yishai Hadas" <yishaih@mellanox.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: leon@kernel.org
Subject: Re: [PATCH v3 0/2] IB/mlx4: Enable debug print of SMPs and enhance output for MADs
Date: Tue, 16 Oct 2018 14:23:55 -0400 [thread overview]
Message-ID: <5393ae97b20baf19e9352c3b3a155d83076e67e5.camel@redhat.com> (raw)
In-Reply-To: <20181009132740.2210085-1-Haakon.Bugge@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Tue, 2018-10-09 at 15:27 +0200, Håkon Bugge wrote:
> SMPs were not printed at all. Added printing of port number and TID to
> all MADs
>
>
> Håkon Bugge (2):
> IB/mlx4: Enable debug print of SMPs
> IB/mlx4: Add port and TID to MAD debug print
>
> drivers/infiniband/hw/mlx4/mad.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> --
>
> v1 -> v2
> * Fixed incorrect format for printing the TID for the second patch
> v2 -> v3
> * Made v3 consistently for cover-letter and the two patches, my v2
> was partly original submission plus a v2. That probably fooled
> both the kbuild bot and patchwork
>
> 2.14.3
Thanks, applied.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-10-16 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 13:27 [PATCH v3 0/2] IB/mlx4: Enable debug print of SMPs and enhance output for MADs Håkon Bugge
2018-10-09 13:27 ` [PATCH v3 1/2] IB/mlx4: Enable debug print of SMPs Håkon Bugge
2018-10-09 13:27 ` [PATCH v3 2/2] IB/mlx4: Add port and TID to MAD debug print Håkon Bugge
2018-10-16 18:23 ` Doug Ledford [this message]
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=5393ae97b20baf19e9352c3b3a155d83076e67e5.camel@redhat.com \
--to=dledford@redhat.com \
--cc=Haakon.Bugge@oracle.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).