On 2018-04-26 02:44, Frank Rowand wrote:
> On 04/25/18 17:32, Frank Rowand wrote:
>> Hi Jan,
>>
>> On 04/24/18 13:58, Frank Rowand wrote:
>>> On 04/24/18 10:50, Jan Kiszka wrote:
On 2018-04-24 19:44, Frank Rowand wrote:
> On 04/24/18 09:19, Jan Kiszka wrote:
>> Only the overlay
On 2018-04-26 02:44, Frank Rowand wrote:
> On 04/25/18 17:32, Frank Rowand wrote:
>> Hi Jan,
>>
>> On 04/24/18 13:58, Frank Rowand wrote:
>>> On 04/24/18 10:50, Jan Kiszka wrote:
On 2018-04-24 19:44, Frank Rowand wrote:
> On 04/24/18 09:19, Jan Kiszka wrote:
>> Only the overlay
On 04/25/18 17:32, Frank Rowand wrote:
> Hi Jan,
>
> On 04/24/18 13:58, Frank Rowand wrote:
>> On 04/24/18 10:50, Jan Kiszka wrote:
>>> On 2018-04-24 19:44, Frank Rowand wrote:
On 04/24/18 09:19, Jan Kiszka wrote:
> Only the overlay notifier callbacks have a chance to potentially get
On 04/25/18 17:32, Frank Rowand wrote:
> Hi Jan,
>
> On 04/24/18 13:58, Frank Rowand wrote:
>> On 04/24/18 10:50, Jan Kiszka wrote:
>>> On 2018-04-24 19:44, Frank Rowand wrote:
On 04/24/18 09:19, Jan Kiszka wrote:
> Only the overlay notifier callbacks have a chance to potentially get
Hi Jan,
On 04/24/18 13:58, Frank Rowand wrote:
> On 04/24/18 10:50, Jan Kiszka wrote:
>> On 2018-04-24 19:44, Frank Rowand wrote:
>>> On 04/24/18 09:19, Jan Kiszka wrote:
Only the overlay notifier callbacks have a chance to potentially get
hold of references to those two resources, but
Hi Jan,
On 04/24/18 13:58, Frank Rowand wrote:
> On 04/24/18 10:50, Jan Kiszka wrote:
>> On 2018-04-24 19:44, Frank Rowand wrote:
>>> On 04/24/18 09:19, Jan Kiszka wrote:
Only the overlay notifier callbacks have a chance to potentially get
hold of references to those two resources, but
On 04/24/18 10:50, Jan Kiszka wrote:
> On 2018-04-24 19:44, Frank Rowand wrote:
>> On 04/24/18 09:19, Jan Kiszka wrote:
>>> Only the overlay notifier callbacks have a chance to potentially get
>>> hold of references to those two resources, but they do not store them.
>>> So it is safe to stop the
On 04/24/18 10:50, Jan Kiszka wrote:
> On 2018-04-24 19:44, Frank Rowand wrote:
>> On 04/24/18 09:19, Jan Kiszka wrote:
>>> Only the overlay notifier callbacks have a chance to potentially get
>>> hold of references to those two resources, but they do not store them.
>>> So it is safe to stop the
On 2018-04-24 19:44, Frank Rowand wrote:
> On 04/24/18 09:19, Jan Kiszka wrote:
>> Only the overlay notifier callbacks have a chance to potentially get
>> hold of references to those two resources, but they do not store them.
>> So it is safe to stop the intentional leaking.
>>
>> See also
On 2018-04-24 19:44, Frank Rowand wrote:
> On 04/24/18 09:19, Jan Kiszka wrote:
>> Only the overlay notifier callbacks have a chance to potentially get
>> hold of references to those two resources, but they do not store them.
>> So it is safe to stop the intentional leaking.
>>
>> See also
On 04/24/18 09:19, Jan Kiszka wrote:
> Only the overlay notifier callbacks have a chance to potentially get
> hold of references to those two resources, but they do not store them.
> So it is safe to stop the intentional leaking.
>
> See also https://lkml.org/lkml/2018/4/23/1063 and following.
>
On 04/24/18 09:19, Jan Kiszka wrote:
> Only the overlay notifier callbacks have a chance to potentially get
> hold of references to those two resources, but they do not store them.
> So it is safe to stop the intentional leaking.
>
> See also https://lkml.org/lkml/2018/4/23/1063 and following.
>
Only the overlay notifier callbacks have a chance to potentially get
hold of references to those two resources, but they do not store them.
So it is safe to stop the intentional leaking.
See also https://lkml.org/lkml/2018/4/23/1063 and following.
Signed-off-by: Jan Kiszka
Only the overlay notifier callbacks have a chance to potentially get
hold of references to those two resources, but they do not store them.
So it is safe to stop the intentional leaking.
See also https://lkml.org/lkml/2018/4/23/1063 and following.
Signed-off-by: Jan Kiszka
---
Ideally, we sort
14 matches
Mail list logo
