All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: 禹舟键 <ufo19890607@gmail.com>
Cc: akpm@linux-foundation.org, rientjes@google.com,
	kirill.shutemov@linux.intel.com, aarcange@redhat.com,
	penguin-kernel@i-love.sakura.ne.jp, guro@fb.com,
	yang.s@alibaba-inc.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	Wind Yu <yuzhoujian@didichuxing.com>
Subject: Re: [PATCH v13 2/2] Add oom victim's memcg to the oom context information
Date: Wed, 11 Jul 2018 09:53:46 +0200	[thread overview]
Message-ID: <20180711074933.GA20050@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHCio2jQO58+npS269Ufyg17unHUeKDRpVjS4-ggBEV8xFMMqQ@mail.gmail.com>

On Wed 11-07-18 11:39:29, 禹舟键 wrote:
> Hi Michal
> Sorry , I l forget to update the changlog for the second patch, but
> the cpuset information is not missing.

The cpuset information is missing in the changelog.

> Do I still need to make the
> v14  or just update the changelog for v13?

Wait for more feedback for few days. If there are no other concerns just
repost this patch 2. Btw. I still think that it would be more logical
to print cpuset before memcg info. But I will not insist.
-- 
Michal Hocko
SUSE Labs

WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: 禹舟键 <ufo19890607@gmail.com>
Cc: akpm@linux-foundation.org, rientjes@google.com,
	kirill.shutemov@linux.intel.com, aarcange@redhat.com,
	penguin-kernel@i-love.sakura.ne.jp, guro@fb.com,
	yang.s@alibaba-inc.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	Wind Yu <yuzhoujian@didichuxing.com>
Subject: Re: [PATCH v13 2/2] Add oom victim's memcg to the oom context information
Date: Wed, 11 Jul 2018 09:53:46 +0200	[thread overview]
Message-ID: <20180711074933.GA20050@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHCio2jQO58+npS269Ufyg17unHUeKDRpVjS4-ggBEV8xFMMqQ@mail.gmail.com>

On Wed 11-07-18 11:39:29, c|1e??e?(R) wrote:
> Hi Michal
> Sorry , I l forget to update the changlog for the second patch, but
> the cpuset information is not missing.

The cpuset information is missing in the changelog.

> Do I still need to make the
> v14  or just update the changelog for v13?

Wait for more feedback for few days. If there are no other concerns just
repost this patch 2. Btw. I still think that it would be more logical
to print cpuset before memcg info. But I will not insist.
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2018-07-11  7:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 10:19 [PATCH v13 1/2] Reorganize the oom report in dump_header ufo19890607
2018-07-10 10:19 ` [PATCH v13 2/2] Add oom victim's memcg to the oom context information ufo19890607
2018-07-10 12:08   ` Michal Hocko
2018-07-11  3:39     ` 禹舟键
2018-07-11  7:53       ` Michal Hocko [this message]
2018-07-11  7:53         ` Michal Hocko
2018-07-11 10:31         ` 禹舟键
2018-07-11 11:10           ` Michal Hocko
2018-07-11 11:10             ` Michal Hocko
2018-07-10 12:03 ` [PATCH v13 1/2] Reorganize the oom report in dump_header Michal Hocko
2018-07-13  5:06 ` [lkp-robot] 0a8f358b50: BUG:KASAN:null-ptr-deref_in_d kernel test robot
2018-07-13 11:55 [PATCH v13 2/2] Add oom victim's memcg to the oom context information ufo19890607
2018-07-13 13:13 ` Michal Hocko
2018-07-13 22:22 ` David Rientjes
2018-07-15  1:08   ` 禹舟键
2018-07-17  3:51     ` David Rientjes
2018-07-17  3:51       ` David Rientjes

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=20180711074933.GA20050@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=guro@fb.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=rientjes@google.com \
    --cc=ufo19890607@gmail.com \
    --cc=yang.s@alibaba-inc.com \
    --cc=yuzhoujian@didichuxing.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.