mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Rientjes <rientjes@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Revert needed: udev spewing warnons on common systems in 3.0
Date: Tue, 2 Aug 2011 10:16:14 +0100	[thread overview]
Message-ID: <20110802101614.009cdf42@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1108011916480.15596@chino.kir.corp.google.com>

> It was a printk_once() when the tunable was scheduled to be removed two 
> years later.  Now that one year has passed since the oom killer rewrite 
> has been merged, it was changed to a WARN_ONCE() simply to attract more 
> attention to the issue. 

For the most part the only people whose attention you need are the
distributions not the end users so the WARN isn't helpful.

Alan

  reply	other threads:[~2011-08-02  9:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02  0:52 Andi Kleen
2011-08-02  1:32 ` Andrew Morton
2011-08-02  1:41   ` Linus Torvalds
2011-08-02  2:22     ` David Rientjes
2011-08-02  9:16       ` Alan Cox [this message]
2011-08-02  9:53         ` David Rientjes
2011-08-02 10:11           ` Alan Cox
2011-08-02 11:22             ` David Miller
2011-08-02 14:45             ` Andi Kleen
2011-08-02 21:50               ` David Rientjes
2011-08-02 21:45             ` David Rientjes
2011-08-02 22:06               ` Andi Kleen
2011-08-02 11:20           ` David Miller
2011-08-02  2:34 ` David Rientjes
2011-08-02  6:07   ` Andi Kleen
2011-08-02  9:54     ` [patch] oom: change warning for deprecated oom_adj to avoid WARN_ONCE() David Rientjes
2011-08-03  6:10       ` Borislav Petkov
2011-08-04  6:04         ` David Rientjes
2011-08-04  7:48           ` Borislav Petkov

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=20110802101614.009cdf42@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@google.com \
    --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
all inboxes | Powered by JetHome®