All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Sasha Levin <Alexander.Levin@microsoft.com>,
	Michal Hocko <mhocko@kernel.org>, Michal Hocko <mhocko@suse.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] memcg: fix per_node_info cleanup
Date: Tue, 10 Apr 2018 13:50:30 +0000	[thread overview]
Message-ID: <DM5PR2101MB103201ED48A7DFF9C1CC2366FBBE0@DM5PR2101MB1032.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20180406100906.17790-1-mhocko@kernel.org>

Hi,

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 00f3ca2c2d66 mm: memcontrol: per-lruvec stats infrastructure.

The bot has also determined it's probably a bug fixing patch. (score: 40.3266)

The bot has tested the following trees: v4.16.1, v4.15.16, v4.14.33.

v4.16.1: Build OK!
v4.15.16: Failed to apply! Possible dependencies:
    a983b5ebee57 ("mm: memcontrol: fix excessive complexity in memory.stat reporting")

v4.14.33: Failed to apply! Possible dependencies:
    a983b5ebee57 ("mm: memcontrol: fix excessive complexity in memory.stat reporting")


--
Thanks,
Sasha

  reply	other threads:[~2018-04-10 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 10:09 [PATCH] memcg: fix per_node_info cleanup Michal Hocko
2018-04-06 10:09 ` Michal Hocko
2018-04-10 13:50 ` Sasha Levin [this message]
2018-04-10 14:01   ` Michal Hocko
2018-04-10 17:55     ` Sasha Levin
2018-04-10 20:37       ` Michal Hocko

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=DM5PR2101MB103201ED48A7DFF9C1CC2366FBBE0@DM5PR2101MB1032.namprd21.prod.outlook.com \
    --to=alexander.levin@microsoft.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=mhocko@kernel.org \
    --cc=mhocko@suse.com \
    --cc=stable@vger.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.