From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v2] librdmacm: Make some functions report proper errno
Date: Mon, 21 Dec 2020 09:26:34 +0800 [thread overview]
Message-ID: <5FDFF9CA.1060109@cn.fujitsu.com> (raw)
In-Reply-To: <20201216095549.GC1060282@unreal>
On 2020/12/16 17:55, Leon Romanovsky wrote:
> On Wed, Dec 16, 2020 at 05:51:46PM +0800, Xiao Yang wrote:
>> Hi Leon,
>>
>> Thanks for your quick reply. :-)
>> I have done the same change on three
>> functions(ucma_get_device,ucma_create_cqs, rdma_create_qp_ex).
>>
>> On 2020/12/16 17:22, Xiao Yang wrote:
>>> Some functions reports fixed ENOMEM when getting any failure, so
>>> it's hard for user to know which actual error happens on them.
>>>
>>> Fixes(ucma_get_device):
>>> 2ffda7f29913 ("librdmacm: Only allocate verbs resources when needed")
>>> 191c9346f335 ("librdmacm: Reference count access to verbs context")
>>> Fixes(ucma_create_cqs):
>>> f8f1335ad8d8 ("librdmacm: make CQs optional for rdma_create_qp")
>>> 9e33488e8e50 ("librdmacm: fix all calls to set errno")
>>> Fixes(rdma_create_qp_ex):
>>> d2efdede11f7 ("r4019: Add support for userspace RDMA connection management abstraction (CMA)")
>>> 4e33a4109a62 ("librdmacm: returns errors from the library consistently")
>>> 995eb0c90c1a ("rdmacm: Add support for XRC QPs")
>> For every function, I am not sure which one is an exact commit so just
>> attach all related commits ids.
> No problem, I'll try to sort it out now.
Hi Leon,
Sorry to bother you.
Is there anything blocking the patch? :-)
Best Regards,
Xiao Yang
> Thanks
>
>
> .
>
next prev parent reply other threads:[~2020-12-21 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 9:22 [PATCH v2] librdmacm: Make some functions report proper errno Xiao Yang
2020-12-16 9:51 ` Xiao Yang
2020-12-16 9:55 ` Leon Romanovsky
2020-12-21 1:26 ` Xiao Yang [this message]
2020-12-21 11:42 ` Leon Romanovsky
2020-12-22 3:40 ` 答复: " Yang, Xiao
2020-12-22 8:33 ` 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=5FDFF9CA.1060109@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=leon@kernel.org \
--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