From: Andrew Morton <akpm@linux-foundation.org>
To: Roman Gushchin <guro@fb.com>
Cc: Greg KH <greg@kroah.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Michal Hocko <mhocko@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Yafang Shao <laoar.shao@gmail.com>
Subject: Re: [PATCH] Partially revert "mm/memcontrol.c: keep local VM counters in sync with the hierarchical ones"
Date: Sat, 24 Aug 2019 12:57:50 -0700 [thread overview]
Message-ID: <20190824125750.da9f0aac47cc0a362208f9ff@linux-foundation.org> (raw)
In-Reply-To: <20190817191518.GB11125@castle>
On Sat, 17 Aug 2019 19:15:23 +0000 Roman Gushchin <guro@fb.com> wrote:
> > > Fixes: 766a4c19d880 ("mm/memcontrol.c: keep local VM counters in sync with the hierarchical ones")
> > > Signed-off-by: Roman Gushchin <guro@fb.com>
> > > Cc: Yafang Shao <laoar.shao@gmail.com>
> > > Cc: Johannes Weiner <hannes@cmpxchg.org>
> > > ---
> > > mm/memcontrol.c | 8 +++-----
> > > 1 file changed, 3 insertions(+), 5 deletions(-)
> >
> > <formletter>
> >
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree. Please read:
> > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for how to do this properly.
>
> Oh, I'm sorry, will read and follow next time. Thanks!
766a4c19d880 is not present in 5.2 so no -stable backport is needed, yes?
next prev parent reply other threads:[~2019-08-24 19:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 0:47 Roman Gushchin
2019-08-17 3:33 ` Yafang Shao
2019-08-17 19:14 ` Roman Gushchin
2019-08-18 0:30 ` Yafang Shao
2019-08-19 21:20 ` Roman Gushchin
2019-08-20 1:29 ` Yafang Shao
2019-08-17 6:36 ` Greg KH
2019-08-17 19:15 ` Roman Gushchin
2019-08-24 19:57 ` Andrew Morton [this message]
2019-08-24 20:23 ` Thomas Backlund
2019-08-27 14:10 ` Michal Hocko
2019-08-27 17:06 ` Greg KH
2019-08-27 17:39 ` Michal Hocko
2019-08-27 18:39 ` Greg KH
2019-08-23 22:33 ` Roman Gushchin
2019-08-24 3:41 ` Yafang Shao
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=20190824125750.da9f0aac47cc0a362208f9ff@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Kernel-team@fb.com \
--cc=greg@kroah.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox