On Tue, May 15, 2018 at 07:05:53PM +0300, Mike Rapoport wrote:
> The new test verifies that memory.swap.max and memory.swap.current behave
> as expected for simple allocation scenarios
> 
> Signed-off-by: Mike Rapoport <[email protected]>
> ---
> 
> The patch is against kselftest/next branch

Hi Mike!

Looks good to me, thank you for working on it!

Acked-by: Roman Gushchin <[email protected]>

Reply via email to