From: Leon Romanovsky <leon@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: Maxim Samoylov <max7255@meta.com>,
Bernard Metzler <bmt@zurich.ibm.com>,
Guoqing Jiang <guoqing.jiang@linux.dev>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Christian Benvenuti <benve@cisco.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>
Subject: Re: [PATCH v2] IB: rework memlock limit handling code
Date: Sun, 5 Nov 2023 12:21:05 +0200 [thread overview]
Message-ID: <20231105102105.GB11062@unreal> (raw)
In-Reply-To: <daf453fa-c834-9cf1-0ddc-04abdfa37abb@cornelisnetworks.com>
On Thu, Nov 02, 2023 at 04:54:22PM -0400, Dennis Dalessandro wrote:
> On 11/2/23 8:32 AM, Leon Romanovsky wrote:
> >>
> >> So, as for 31.10.2023 I still see siw_umem_get() call used in
> >> linux-rdma repo in "for-next" branch.
> >
> > I hoped to hear some feedback from Bernard and Dennis.
> >
>
> Sorry about that. I thought I did respond about qib.
Dennis, qib probably needs to use ib_umem_get too.
>
> Acked-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
next prev parent reply other threads:[~2023-11-05 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 8:29 [PATCH v2] IB: rework memlock limit handling code Maxim Samoylov
2023-10-15 9:19 ` Leon Romanovsky
2023-10-23 1:40 ` Guoqing Jiang
2023-10-23 5:52 ` Leon Romanovsky
2023-10-31 13:30 ` Maxim Samoylov
2023-11-02 12:32 ` Leon Romanovsky
2023-11-02 13:40 ` Bernard Metzler
2023-11-02 20:54 ` Dennis Dalessandro
2023-11-05 10:21 ` Leon Romanovsky [this message]
2023-11-03 10:18 ` Bernard Metzler
2023-11-05 10:20 ` Leon Romanovsky
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=20231105102105.GB11062@unreal \
--to=leon@kernel.org \
--cc=benve@cisco.com \
--cc=bmt@zurich.ibm.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=guoqing.jiang@linux.dev \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=max7255@meta.com \
--cc=vadim.fedorenko@linux.dev \
/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.