From: Greg KH <gregkh@linuxfoundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Stable tree <stable@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH stable 4.4 2/4] mm: filemap: don't plant shadow entries without radix tree node
Date: Wed, 26 Oct 2016 15:10:49 +0200 [thread overview]
Message-ID: <20161026131049.GA7657@kroah.com> (raw)
In-Reply-To: <20161026124753.GG18382@dhcp22.suse.cz>
On Wed, Oct 26, 2016 at 02:47:53PM +0200, Michal Hocko wrote:
> On Wed 26-10-16 14:45:53, Michal Hocko wrote:
> > Greg,
> > I do not see this one in the 4.4 queue you have just sent today.
>
> Scratch that. I can see it now on lkml. I just wasn't on the CC so it
> hasn't shown up in my inbox.
Sorry about that, I had applied it earlier in the sequence due to it
being part of the "normal" stable request process.
thanks,
greg k-h
next prev parent reply other threads:[~2016-10-26 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 7:51 [PATCH stable 4.4 0/4] mm: workingset backports Michal Hocko
2016-10-25 7:51 ` [PATCH stable 4.4 1/4] mm: workingset: fix crash in shadow node shrinker caused by replace_page_cache_page() Michal Hocko
2016-10-25 7:51 ` [PATCH stable 4.4 2/4] mm: filemap: don't plant shadow entries without radix tree node Michal Hocko
2016-10-26 12:45 ` Michal Hocko
2016-10-26 12:47 ` Michal Hocko
2016-10-26 13:10 ` Greg KH [this message]
2016-10-25 7:51 ` [PATCH stable 4.4 3/4] mm: filemap: fix mapping->nrpages double accounting in fuse Michal Hocko
2016-10-25 7:51 ` [PATCH stable 4.4 4/4] Using BUG_ON() as an assert() is _never_ acceptable Michal Hocko
2016-10-25 7:56 ` [PATCH stable 4.4 0/4] mm: workingset backports Michal Hocko
2016-10-25 14:16 ` Johannes Weiner
2016-10-26 9:34 ` Greg KH
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=20161026131049.GA7657@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).