From: Jason Gunthorpe <jgg@nvidia.com>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: <dledford@redhat.com>, <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH for-next v2 0/2] RDMA/bnxt_re: Allow bigger user MRs
Date: Mon, 18 Jan 2021 17:01:29 -0400 [thread overview]
Message-ID: <20210118210129.GC797553@nvidia.com> (raw)
In-Reply-To: <1610012608-14528-1-git-send-email-selvin.xavier@broadcom.com>
On Thu, Jan 07, 2021 at 01:43:26AM -0800, Selvin Xavier wrote:
> Refactor user space MR code to handle bigger MRs. Removes couple of checks
> that prevented the bigger MRs.
>
> v1->v2:
> - Fix the build warning
> Reported-by: kernel test robot <lkp@intel.com>
>
> Selvin Xavier (2):
> RDMA/bnxt_re: Code refactor while populating user MRs
> RDMA/bnxt_re: Allow bigger MR creation
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-01-18 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 9:43 [PATCH for-next v2 0/2] RDMA/bnxt_re: Allow bigger user MRs Selvin Xavier
2021-01-07 9:43 ` [PATCH for-next v2 1/2] RDMA/bnxt_re: Code refactor while populating " Selvin Xavier
2021-01-07 9:43 ` [PATCH for-next v2 2/2] RDMA/bnxt_re: Allow bigger MR creation Selvin Xavier
2021-01-18 21:01 ` 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=20210118210129.GC797553@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.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 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.