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 V3 for-next 0/3] Broadcom's roce driver bug fixes
Date: Thu, 21 Nov 2019 01:22:20 -0500 [thread overview]
Message-ID: <1574317343-23300-1-git-send-email-devesh.sharma@broadcom.com> (raw)
This submission for for-next branch contains 3 patches, first two
patches are important urgent fixes for Gen P5 device. The first
patch deals with device detection in device open. While second
patch fixes hardware counters.
The third patch fixes few sparse warnings from main.c.
changes from V2 to V3
- moved the series from for-rc to for-next
- added back the sparse warning fix patch.
changes from V1 to V2
- dropped patch related to sparse warnings.
- updated patch description to report the motivation
for submission to for-rc branch.
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-21 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 6:22 Devesh Sharma [this message]
2019-11-21 6:22 ` [PATCH V3 for-next 1/3] RDMA/bnxt_re: Fix chip number validation Broadcom's Gen P5 series Devesh Sharma
2019-11-21 6:22 ` [PATCH V3 for-next 2/3] RDMA/bnxt_re: fix stat push into dma buffer on gen p5 devices Devesh Sharma
2019-11-21 6:22 ` [PATCH V3 for-next 3/3] RDMA/bnxt_re: fix sparse warnings Devesh Sharma
2019-11-22 20:23 ` [PATCH V3 for-next 0/3] Broadcom's roce driver bug fixes Jason Gunthorpe
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=1574317343-23300-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.