From: Jason Gunthorpe <jgg@ziepe.ca>
To: Devesh Sharma <devesh.sharma@broadcom.com>
Cc: linux-rdma@vger.kernel.org, dledford@redhat.com
Subject: Re: [PATCH V2 for-next 0/8] Refactor control path of bnxt_re driver
Date: Thu, 13 Feb 2020 16:17:43 -0400 [thread overview]
Message-ID: <20200213201743.GA24648@ziepe.ca> (raw)
In-Reply-To: <1580407982-882-1-git-send-email-devesh.sharma@broadcom.com>
On Thu, Jan 30, 2020 at 01:12:54PM -0500, Devesh Sharma wrote:
> This is the first series out of few more forthcoming series to refactor
> Broadcom's RoCE driver. This series contains patches to refactor control
> path. Since this is first series, there may be few code section which may
> look redundant or overkill but those will be taken care in future patch
> series.
>
> These patches apply clean on tip of for-next branch.
> Each patch in this series is tested against user and kernel functionality.
These don't apply to for-next, please respin them
Applying: RDMA/bnxt_re: Refactor queue pair creation code
Applying: RDMA/bnxt_re: Replace chip context structure with pointer
Applying: RDMA/bnxt_re: Refactor hardware queue memory allocation
Applying: RDMA/bnxt_re: Refactor net ring allocation function
Applying: RDMA/bnxt_re: Refactor command queue management code
Using index info to reconstruct a base tree...
M drivers/infiniband/hw/bnxt_re/qplib_rcfw.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/infiniband/hw/bnxt_re/qplib_rcfw.c
CONFLICT (content): Merge conflict in drivers/infiniband/hw/bnxt_re/qplib_rcfw.c
Thanks,
Jason
next prev parent reply other threads:[~2020-02-13 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 18:12 [PATCH V2 for-next 0/8] Refactor control path of bnxt_re driver Devesh Sharma
2020-01-30 18:12 ` [PATCH V2 for-next 1/8] RDMA/bnxt_re: Refactor queue pair creation code Devesh Sharma
2020-01-30 18:12 ` [PATCH V2 for-next 2/8] RDMA/bnxt_re: Replace chip context structure with pointer Devesh Sharma
2020-01-30 18:12 ` [PATCH V2 for-next 3/8] RDMA/bnxt_re: Refactor hardware queue memory allocation Devesh Sharma
2020-01-30 18:12 ` [PATCH V2 for-next 4/8] RDMA/bnxt_re: Refactor net ring allocation function Devesh Sharma
2020-01-30 18:12 ` [PATCH V2 for-next 5/8] RDMA/bnxt_re: Refactor command queue management code Devesh Sharma
2020-01-30 18:13 ` [PATCH V2 for-next 6/8] RDMA/bnxt_re: Refactor notification " Devesh Sharma
2020-01-30 18:13 ` [PATCH V2 for-next 7/8] RDMA/bnxt_re: Refactor doorbell management functions Devesh Sharma
2020-01-30 18:13 ` [PATCH V2 for-next 8/8] RDMA/bnxt_re: use ibdev based message printing functions Devesh Sharma
2020-02-13 20:17 ` Jason Gunthorpe [this message]
2020-02-14 5:24 ` [PATCH V2 for-next 0/8] Refactor control path of bnxt_re driver 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=20200213201743.GA24648@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 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.