From: David Rientjes <rientjes@google.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Florian Mickler <florian@mickler.org>,
Valdis.Kletnieks@vt.edu, Jesper Juhl <jj@chaosbits.net>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Ying Han <yinghan@google.com>, Bodo Eggert <7eggert@web.de>,
Mandeep Singh Baines <msb@google.com>,
"Figo.zhang" <figo1802@gmail.com>
Subject: Re: [PATCH] Revert oom rewrite series
Date: Tue, 16 Nov 2010 12:57:21 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1011161255430.1193@chino.kir.corp.google.com> (raw)
In-Reply-To: <20101116145551.49c47df5@lxorguk.ukuu.org.uk>
On Tue, 16 Nov 2010, Alan Cox wrote:
> Yes - so why is it spewing crap, annoying users and trying to irritate
> application authors. It's not 2012 yet.
>
It's a WARN_ON_ONCE() so it will only spew a single line as a reminder
that the application needs to be updated; would you prefer that to be
suppressed until a year before removal, for example?
next prev parent reply other threads:[~2010-11-16 20:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 5:07 [PATCH] Revert oom rewrite series KOSAKI Motohiro
2010-11-14 19:32 ` Linus Torvalds
2010-11-15 0:54 ` KOSAKI Motohiro
2010-11-15 2:19 ` Andrew Morton
[not found] ` <AANLkTik_SDaiu2eQsJ9+4ywLR5K5V1Od-hwop6gwas3F@mail.gmail.com>
2010-11-15 4:41 ` Figo.zhang
2010-11-15 6:57 ` KOSAKI Motohiro
2010-11-15 10:34 ` David Rientjes
2010-11-15 23:31 ` Jesper Juhl
2010-11-16 0:06 ` David Rientjes
2010-11-16 10:04 ` Martin Knoblauch
2010-11-16 10:33 ` Alessandro Suardi
2010-11-16 0:13 ` Valdis.Kletnieks
2010-11-16 6:43 ` David Rientjes
2010-11-16 11:03 ` Alan Cox
2010-11-16 13:03 ` Florian Mickler
2010-11-16 14:55 ` Alan Cox
2010-11-16 20:57 ` David Rientjes [this message]
2010-11-16 21:01 ` Fabio Comolli
2010-11-17 4:04 ` Valdis.Kletnieks
2010-11-16 15:15 ` Alejandro Riveira Fernández
2010-11-23 7:16 ` KOSAKI Motohiro
2010-11-28 1:45 ` David Rientjes
2010-11-30 13:04 ` KOSAKI Motohiro
2010-11-30 20:02 ` David Rientjes
2010-11-23 7:16 ` KOSAKI Motohiro
2010-11-23 23:51 ` KOSAKI Motohiro
2010-11-14 21:58 ` David Rientjes
2010-11-15 23:33 ` Bodo Eggert
2010-11-15 23:50 ` David Rientjes
2010-11-17 0:06 ` Bodo Eggert
2010-11-17 0:25 ` David Rientjes
2010-11-17 0:48 ` Mandeep Singh Baines
-- strict thread matches above, loose matches on Subject: below --
2010-11-10 15:14 [PATCH v3]mm/oom-kill: direct hardware access processes should get bonus Figo.zhang
2010-11-10 15:24 ` Figo.zhang
2010-11-14 5:21 ` KOSAKI Motohiro
2010-11-14 21:33 ` David Rientjes
2010-11-15 3:26 ` [PATCH] Revert oom rewrite series Figo.zhang
2010-11-15 10:14 ` David Rientjes
2010-11-15 10:57 ` Alan Cox
2010-11-15 20:54 ` David Rientjes
2010-11-23 7:16 ` KOSAKI Motohiro
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=alpine.DEB.2.00.1011161255430.1193@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=7eggert@web.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=figo1802@gmail.com \
--cc=florian@mickler.org \
--cc=jj@chaosbits.net \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=msb@google.com \
--cc=torvalds@linux-foundation.org \
--cc=yinghan@google.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;
as well as URLs for NNTP newsgroup(s).