All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: cgroups@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
	Roman Gushchin <guro@fb.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>,
	Jay Kamat <jgkamat@fb.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] kselftest/cgroup: fix unexpected testing failure on test_memcontrol
Date: Fri, 24 May 2019 14:40:35 -0700	[thread overview]
Message-ID: <20190524214035.GG374014@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20190520030140.203605-2-alex.shi@linux.alibaba.com>

Hello,

All three patches look good to me.  Please feel free to add my
acked-by.  Shuah, should I route these through cgroup tree or would
the kselftest tree be a better fit?

Thanks.

-- 
tejun

WARNING: multiple messages have this Message-ID (diff)
From: tj at kernel.org (Tejun Heo)
Subject: [PATCH v2 1/3] kselftest/cgroup: fix unexpected testing failure on test_memcontrol
Date: Fri, 24 May 2019 14:40:35 -0700	[thread overview]
Message-ID: <20190524214035.GG374014@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20190520030140.203605-2-alex.shi@linux.alibaba.com>

Hello,

All three patches look good to me.  Please feel free to add my
acked-by.  Shuah, should I route these through cgroup tree or would
the kselftest tree be a better fit?

Thanks.

-- 
tejun

WARNING: multiple messages have this Message-ID (diff)
From: tj@kernel.org (Tejun Heo)
Subject: [PATCH v2 1/3] kselftest/cgroup: fix unexpected testing failure on test_memcontrol
Date: Fri, 24 May 2019 14:40:35 -0700	[thread overview]
Message-ID: <20190524214035.GG374014@devbig004.ftw2.facebook.com> (raw)
Message-ID: <20190524214035.gRePLNuW8ToZo_ZndRUxKGkdW4-7xxIBDaRPZ9n2xbU@z> (raw)
In-Reply-To: <20190520030140.203605-2-alex.shi@linux.alibaba.com>

Hello,

All three patches look good to me.  Please feel free to add my
acked-by.  Shuah, should I route these through cgroup tree or would
the kselftest tree be a better fit?

Thanks.

-- 
tejun

  reply	other threads:[~2019-05-24 21:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190520030140.203605-1-alex.shi@linux.alibaba.com>
2019-05-20  3:01 ` [PATCH v2 1/3] kselftest/cgroup: fix unexpected testing failure on test_memcontrol Alex Shi
2019-05-20  3:01   ` Alex Shi
2019-05-20  3:01   ` alex.shi
2019-05-24 21:40   ` Tejun Heo [this message]
2019-05-24 21:40     ` Tejun Heo
2019-05-24 21:40     ` tj
2019-05-24 21:44     ` shuah
2019-05-24 21:44       ` shuah
2019-05-24 21:44       ` shuah
2019-05-25  0:06       ` shuah
2019-05-25  0:06         ` shuah
2019-05-25  0:06         ` shuah
2019-05-27  6:30         ` Alex Shi
2019-05-27  6:30           ` Alex Shi
2019-05-27  6:30           ` alex.shi
2019-05-20  3:01 ` [PATCH v2 2/3] kselftest/cgroup: fix unexpected testing failure on test_core Alex Shi
2019-05-20  3:01   ` Alex Shi
2019-05-20  3:01   ` alex.shi
2019-05-20  3:01 ` [PATCH v2 3/3] kselftest/cgroup: fix incorrect test_core skip Alex Shi
2019-05-20  3:01   ` Alex Shi
2019-05-20  3:01   ` alex.shi

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=20190524214035.GG374014@devbig004.ftw2.facebook.com \
    --to=tj@kernel.org \
    --cc=alex.shi@linux.alibaba.com \
    --cc=cgroups@vger.kernel.org \
    --cc=guro@fb.com \
    --cc=jgkamat@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=shuah@kernel.org \
    /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.