On 4/24/2018 4:25 AM, Dag Moxnes wrote:
I was going to suggest the following correction:
If all agree that this is the correct way of doing it, I can go ahead
and an post it.
Yes please. Go ahead and post your fix.
Regards,
Santosh
P.S: Avoid top posting please.
I was going to suggest the following correction:
If all agree that this is the correct way of doing it, I can go ahead
and an post it.
Regards,
-Dag
On 04/24/2018 01:10 PM, Håkon Bugge wrote:
On 24 Apr 2018, at 05:27, santosh.shilim...@oracle.com wrote:
On 4/23/18 6:39 PM, Zhu Yanjun
> On 24 Apr 2018, at 05:27, santosh.shilim...@oracle.com wrote:
>
> On 4/23/18 6:39 PM, Zhu Yanjun wrote:
>> This reverts commit 3b12f73a5c2977153f28a224392fd4729b50d1dc.
>> After long time discussion and investigations, it seems that there
>> is no mem leak. So this patch is reverted.
>>
On 4/23/18 6:39 PM, Zhu Yanjun wrote:
This reverts commit 3b12f73a5c2977153f28a224392fd4729b50d1dc.
After long time discussion and investigations, it seems that there
is no mem leak. So this patch is reverted.
Signed-off-by: Zhu Yanjun
---
Well your fix was not for any
This reverts commit 3b12f73a5c2977153f28a224392fd4729b50d1dc.
After long time discussion and investigations, it seems that there
is no mem leak. So this patch is reverted.
Signed-off-by: Zhu Yanjun
---
net/rds/ib_cm.c | 47 +++