From: Devesh Sharma <devesh.sharma@broadcom.com>
To: dledford@redhat.com, jgg@mellanox.com
Cc: linux-rdma@vger.kernel.org, Devesh Sharma <devesh.sharma@broadcom.com>
Subject: [PATCH for-rc 0/3] Broadcom's roce dirver bug fixes
Date: Tue, 19 Nov 2019 10:48:48 -0500 [thread overview]
Message-ID: <1574178531-15898-1-git-send-email-devesh.sharma@broadcom.com> (raw)
This series contain 3 patches patch 1 and patch 2 are specific to
Gen P5 devices. Patch 3 is a generic fix to silence few sparse
warnings.
changes for V0 to V1
- originally this series had only 1 patch which is the first patch.
- Added Fixes tag on the first patch.
- added two more patches to fix other quick bug fixes.
Devesh Sharma (2):
RDMA/bnxt_re: fix stat push into dma buffer on gen p5 devices
RDMA/bnxt_re: fix sparse warnings
Luke Starrett (1):
RDMA/bnxt_re: Fix chip number validation Broadcom's Gen P5 series
drivers/infiniband/hw/bnxt_re/main.c | 9 +++++----
drivers/infiniband/hw/bnxt_re/qplib_res.h | 8 ++++++--
2 files changed, 11 insertions(+), 6 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-11-19 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 15:48 Devesh Sharma [this message]
2019-11-19 15:48 ` [PATCH for-rc 1/3] RDMA/bnxt_re: Fix chip number validation Broadcom's Gen P5 series Devesh Sharma
2019-11-19 15:48 ` [PATCH for-rc 2/3] RDMA/bnxt_re: fix stat push into dma buffer on gen p5 devices Devesh Sharma
2019-11-19 15:48 ` [PATCH for-rc 3/3] RDMA/bnxt_re: fix sparse warnings Devesh Sharma
2019-11-19 19:38 ` [PATCH for-rc 0/3] Broadcom's roce dirver bug fixes Jason Gunthorpe
2019-11-20 5:22 ` Devesh Sharma
2019-11-20 13:32 ` Jason Gunthorpe
2019-11-20 16:17 ` Devesh Sharma
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=1574178531-15898-1-git-send-email-devesh.sharma@broadcom.com \
--to=devesh.sharma@broadcom.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
/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).