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

From: Tejun Heo <tj@kernel.org>
To: Shuah Khan <shuah@kernel.org>
Cc: Roman Gushchin <guro@fb.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@suse.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>,
	kernel-team@fb.com, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests/cgroup: memory controller self-tests
Date: Fri, 11 May 2018 09:29:20 -0700	[thread overview]
Message-ID: <20180511162920.GV2368884@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <ae4dc3f9-baa6-b492-7c43-0359734440b3@kernel.org>

Hello, Shuah.

On Fri, May 11, 2018 at 08:55:28AM -0600, Shuah Khan wrote:
> I think we don't need to create a special branch and all. The following
> should work:
> 
> linux-next already has the skip work. What we can do is:
> 
> Do the cleanup and test it against linux-next. In linux-next SKIP isn't PASS. If test is
> compiled on linux-next, you will see that SKIP is SKIP. If it is compiled on the mainline,
> it will be reported PASS, which will be a temporary state.

Hah, why not just create a branch and make sure what we see in the
topic branch is what we'll push?  That's how these things are done
usually.

Thanks.

-- 
tejun