From: Michal Hocko <mhocko@suse.cz>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
David Rientjes <rientjes@google.com>, Tejun Heo <tj@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 0/3] OOM vs. freezer interaction fixes
Date: Mon, 13 Oct 2014 17:14:35 +0200 [thread overview]
Message-ID: <20141013151435.GB15129@dhcp22.suse.cz> (raw)
In-Reply-To: <2107592.sy6uXko7kW@vostro.rjw.lan>
On Thu 09-10-14 00:11:33, Rafael J. Wysocki wrote:
> On Wednesday, October 08, 2014 04:07:43 PM Michal Hocko wrote:
> > Hi Andrew, Rafael,
> >
> > this has been originally discussed here [1] but didn't lead anywhere AFAICS
> > so I would like to resurrect them.
>
> OK
>
> So any chance to CC linux-pm too next time? There are people on that list
> who may be interested as well and are not in the CC directly either.
Sure, sorry about that! I've simply used the same CC list as the
previous post without realizing PM list was missing.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-10-13 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 14:07 Michal Hocko
2014-10-08 14:07 ` [PATCH 1/3] freezer: check OOM kill while being frozen Michal Hocko
2014-10-08 14:07 ` [PATCH 2/3] freezer: remove obsolete comments in __thaw_task() Michal Hocko
2014-10-08 14:07 ` [PATCH 3/3] OOM, PM: OOM killed task cannot escape PM suspend Michal Hocko
2014-10-08 22:11 ` [PATCH 0/3] OOM vs. freezer interaction fixes Rafael J. Wysocki
2014-10-13 15:14 ` Michal Hocko [this message]
2014-10-09 4:42 ` Cong Wang
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=20141013151435.GB15129@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=rientjes@google.com \
--cc=rjw@rjwysocki.net \
--cc=tj@kernel.org \
--cc=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox