30/05/2018 18:04, David Marchand:
> On Wed, May 30, 2018 at 5:59 PM, Yongseok Koh wrote:
> >> On May 30, 2018, at 7:42 AM, David Marchand
> >> wrote:
> >>
> >> The callback should be invoked only for memory that has been registered
> >> in a device, hence, no need to track cleanup events if no d
On Wed, May 30, 2018 at 5:59 PM, Yongseok Koh wrote:
>> On May 30, 2018, at 7:42 AM, David Marchand wrote:
>>
>> The callback should be invoked only for memory that has been registered
>> in a device, hence, no need to track cleanup events if no device is
>> present.
>>
>> Bugzilla-ID: 56
>> Fixe
On 5/30/2018 3:42 PM, David Marchand wrote:
> The callback should be invoked only for memory that has been registered
> in a device, hence, no need to track cleanup events if no device is
> present.
>
> Bugzilla-ID: 56
> Fixes: 974f1e7ef146 ("net/mlx5: add new memory region support")
>
> Signed-o
> On May 30, 2018, at 7:42 AM, David Marchand wrote:
>
> The callback should be invoked only for memory that has been registered
> in a device, hence, no need to track cleanup events if no device is
> present.
>
> Bugzilla-ID: 56
> Fixes: 974f1e7ef146 ("net/mlx5: add new memory region support")
The callback should be invoked only for memory that has been registered
in a device, hence, no need to track cleanup events if no device is
present.
Bugzilla-ID: 56
Fixes: 974f1e7ef146 ("net/mlx5: add new memory region support")
Signed-off-by: David Marchand
---
drivers/net/mlx5/mlx5.c | 4 ++--
5 matches
Mail list logo
