From: David Miller <davem@davemloft.net>
To: rientjes@google.com
Cc: alan@lxorguk.ukuu.org.uk, torvalds@linux-foundation.org,
akpm@linux-foundation.org, andi@firstfloor.org,
linux-kernel@vger.kernel.org
Subject: Re: Revert needed: udev spewing warnons on common systems in 3.0
Date: Tue, 02 Aug 2011 04:20:19 -0700 (PDT) [thread overview]
Message-ID: <20110802.042019.719045752884572940.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1108020249560.18935@chino.kir.corp.google.com>
From: David Rientjes <rientjes@google.com>
Date: Tue, 2 Aug 2011 02:53:34 -0700 (PDT)
> That's obviously wrong since all of the applications that I've cited
> that have been fixed to date have been the result of users actually
> noticing the printk_once() and emailing me directly to pass it along to
> the appropriate parties. I've also found other cases where bugzilla
> entries were created based on that single line warning by users, who in
> turn get distros and maintainers to convert to the new interface.
>
> It's quite effective, but there are still some applications that have yet
> to be reported, hence the reason for anybody actually hitting this new
> WARN_ONCE().
I completely agree with you. Printing out some kind of warning does
get the problems fixed.
next prev parent reply other threads:[~2011-08-02 11:20 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
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 [this message]
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=20110802.042019.719045752884572940.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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®