From: Greg KH <gregkh@linuxfoundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, alexander.levin@microsoft.com,
penguin-kernel@I-love.SAKURA.ne.jp,
torvalds@linux-foundation.org, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "oom: improve oom disable handling" has been added to the 4.9-stable tree
Date: Thu, 22 Mar 2018 15:48:41 +0100 [thread overview]
Message-ID: <20180322144841.GA27199@kroah.com> (raw)
In-Reply-To: <20180322141643.GF23100@dhcp22.suse.cz>
On Thu, Mar 22, 2018 at 03:16:43PM +0100, Michal Hocko wrote:
> Greg, this doesn't really look like a fix that should go to the stable
> tree. It doesn't really fix any serious bug.
Thanks for letting me know, now dropped.
greg k-h
prev parent reply other threads:[~2018-03-22 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 13:49 Patch "oom: improve oom disable handling" has been added to the 4.9-stable tree gregkh
2018-03-22 14:16 ` Michal Hocko
2018-03-22 14:48 ` Greg KH [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=20180322144841.GA27199@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@microsoft.com \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=stable-commits@vger.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).