From: Shuah Khan <shuah@kernel.org>
To: jgkamat@fb.com
Cc: linux-kselftest@vger.kernel.org, Roman Gushchin <guro@fb.com>,
Tejun Heo <tj@kernel.org>,
kernel-team@fb.com, linux-kernel@vger.kernel.org,
jaygkamat@gmail.com, Shuah Khan <shuah@kernel.org>
Subject: Re: kselftests for memory.oom.group
Date: Fri, 7 Sep 2018 16:53:06 -0600 [thread overview]
Message-ID: <6d514fa2-4f85-059b-8737-2cd03519156d@kernel.org> (raw)
In-Reply-To: <20180907213405.31574-1-jgkamat@fb.com>
On 09/07/2018 03:34 PM, jgkamat@fb.com wrote:
> Here is the third version of the patchset.
>
> Changes since the last patchset:
> - Updated commit message of first patch to clarify fixes
> - Add ack from Roman
>
> There should be no code changes since the last patchset.
>
> Let me know if any improvements can be made, and thanks for your time!
> -Jay
>
>
Hi Jay,
Thanks for these patches. Applied to linux-kselftest next
-- Shuah
prev parent reply other threads:[~2018-09-07 22:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 1:08 kselftests for memory.oom.group jgkamat
2018-09-05 1:08 ` [PATCH 1/2] Fix cg_read_strcmp() jgkamat
2018-09-05 14:43 ` Shuah Khan
2018-09-05 1:08 ` [PATCH 2/2] Add tests for memory.oom.group jgkamat
2018-09-05 15:21 ` Shuah Khan
2018-09-07 16:49 ` kselftests " jgkamat
2018-09-07 16:49 ` [PATCH 1/2] Fix cg_read_strcmp() jgkamat
2018-09-07 16:56 ` Roman Gushchin
2018-09-07 17:06 ` Shuah Khan
2018-09-07 18:28 ` Jay Kamat
2018-09-07 18:53 ` Shuah Khan
2018-09-07 16:49 ` [PATCH 2/2] Add tests for memory.oom.group jgkamat
2018-09-07 16:57 ` Roman Gushchin
2018-09-07 21:34 ` kselftests " jgkamat
2018-09-07 21:34 ` [PATCH v3 1/2] Fix cg_read_strcmp() jgkamat
2018-09-07 21:34 ` [PATCH v3 2/2] Add tests for memory.oom.group jgkamat
2018-09-07 22:53 ` Shuah Khan [this message]
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=6d514fa2-4f85-059b-8737-2cd03519156d@kernel.org \
--to=shuah@kernel.org \
--cc=guro@fb.com \
--cc=jaygkamat@gmail.com \
--cc=jgkamat@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).