linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Devesh Sharma <devesh.sharma@broadcom.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH V3 for-next 0/3] Broadcom's roce driver bug fixes
Date: Fri, 22 Nov 2019 16:23:12 -0400	[thread overview]
Message-ID: <20191122202312.GA1316@ziepe.ca> (raw)
In-Reply-To: <1574317343-23300-1-git-send-email-devesh.sharma@broadcom.com>

On Thu, Nov 21, 2019 at 01:22:20AM -0500, Devesh Sharma wrote:
> 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.
> 
> 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

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2019-11-22 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21  6:22 [PATCH V3 for-next 0/3] Broadcom's roce driver bug fixes Devesh Sharma
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 ` Jason Gunthorpe [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=20191122202312.GA1316@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=devesh.sharma@broadcom.com \
    --cc=dledford@redhat.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).