From: tj at kernel.org (Tejun Heo)
Subject: [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
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: tj@kernel.org (Tejun Heo)
Subject: [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)
Message-ID: <20180511162920.H1IjjpdHnVpbrJ1dhe52Q4K9ID0AnRt6YVF3E-EiDMU@z> (raw)
In-Reply-To: <ae4dc3f9-baa6-b492-7c43-0359734440b3@kernel.org>
Hello, Shuah.
On Fri, May 11, 2018@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
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
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
next prev parent reply other threads:[~2018-05-11 16:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 16:37 [PATCH v2] selftests/cgroup: memory controller self-tests guro
2018-05-10 16:37 ` Roman Gushchin
2018-05-10 16:37 ` Roman Gushchin
2018-05-10 18:32 ` tj
2018-05-10 18:32 ` Tejun Heo
2018-05-10 18:32 ` Tejun Heo
2018-05-10 19:29 ` shuah
2018-05-10 19:29 ` Shuah Khan
2018-05-10 19:29 ` Shuah Khan
2018-05-11 14:32 ` tj
2018-05-11 14:32 ` Tejun Heo
2018-05-11 14:32 ` Tejun Heo
2018-05-11 14:55 ` shuah
2018-05-11 14:55 ` Shuah Khan
2018-05-11 14:55 ` Shuah Khan
2018-05-11 16:29 ` tj [this message]
2018-05-11 16:29 ` Tejun Heo
2018-05-11 16:29 ` Tejun Heo
2018-05-11 16:58 ` shuah
2018-05-11 16:58 ` Shuah Khan
2018-05-11 16:58 ` Shuah Khan
2018-05-11 18:03 ` guro
2018-05-11 18:03 ` Roman Gushchin
2018-05-11 18:03 ` Roman Gushchin
2018-05-11 19:33 ` shuah
2018-05-11 19:33 ` Shuah Khan
2018-05-11 19:33 ` Shuah Khan
2018-05-11 20:02 ` tj
2018-05-11 20:02 ` Tejun Heo
2018-05-11 20:02 ` Tejun Heo
2018-05-11 20:22 ` shuah
2018-05-11 20:22 ` Shuah Khan
2018-05-11 20:22 ` Shuah Khan
2018-05-18 19:24 ` shuah
2018-05-18 19:24 ` Shuah Khan
2018-05-18 19:24 ` Shuah Khan
2018-05-10 19:45 ` shuah
2018-05-10 19:45 ` Shuah Khan
2018-05-10 19:45 ` Shuah Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180511162920.GV2368884@devbig577.frc2.facebook.com \
--to=unknown@example.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.