linux-kernel - Re: [PATCH v2] selftests/cgroup: memory controller self-tests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180511143228.GU2368884@devbig577.frc2.facebook.com>
Date:   Fri, 11 May 2018 07:32:28 -0700
From:   Tejun Heo <tj@...nel.org>
To:     Shuah Khan <shuah@...nel.org>
Cc:     Roman Gushchin <guro@...com>, Johannes Weiner <hannes@...xchg.org>,
        Michal Hocko <mhocko@...e.com>,
        Mike Rapoport <rppt@...ux.vnet.ibm.com>, kernel-team@...com,
        linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] selftests/cgroup: memory controller self-tests

Hello, Shuah.

On Thu, May 10, 2018 at 01:29:07PM -0600, Shuah Khan wrote:
> Don't pull them yet. If Roman can redo the patches on linux-kselftest next,
> he can pick up the SKIP changes.

So, what we can do is either fix that up during / after the merge
window or creating a separate branch which pulls from both cgroup and
kselftest.  Please let me know which way you wanna go and if the
latter which branch I should pull (it gotta be a stable branch).

Thanks.

-- 
tejun