All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Bodo Eggert <7eggert@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.11.2][RFC] printk with anti-cluttering-feature
Date: Sun, 20 Mar 2005 14:49:39 +0300	[thread overview]
Message-ID: <423D6353.5010603@tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.58.0503200528520.2804@be1.lrz>

Bodo Eggert wrote:
> (I hope I avoided all spam-keywords this time, my previous mails didn't 
>  seem to make it)
> (please CC me on reply)
> 
> Issue:
> 
> On some conditions, the dmesg is spammed with repeated warnings about the
> same issue which is neither critical nor going to be fixed. This may
> result in losing the boot messages or missing other important messages.

There's printk_ratelimit() already, used in quite several places in kernel
(or net_ratelimit() for net/* stuff).  See also Documentation/sysctl/kernel.txt,
search for printk_ratelimit.  JFYI.

/mjt

  parent reply	other threads:[~2005-03-20 11:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20  4:37 [PATCH 2.6.11.2][RFC] printk with anti-cluttering-feature Bodo Eggert
2005-03-20  4:40 ` Trond Myklebust
2005-03-20 11:49 ` Michael Tokarev [this message]
2005-03-20 13:50   ` Bodo Eggert
2005-03-20 21:29     ` [PATCH 2.6.11.2][0/2] " Bodo Eggert
2005-03-20 21:35       ` [PATCH 2.6.11.2][1/2] " Bodo Eggert
2005-03-20 21:43       ` [PATCH 2.6.11.2][2/2] " Bodo Eggert
2005-03-21  8:25         ` Bodo Eggert
2005-03-25  0:45           ` Bodo Eggert
2005-03-20 21:45       ` [PATCH 2.6.11.2][SECURITY] " Bodo Eggert
2005-03-21 14:58 ` [PATCH 2.6.11.2][RFC] " Andi Kleen
2005-03-21 15:39   ` Hugh Dickins
2005-03-21 18:50   ` Bodo Eggert
2005-03-25  0:23   ` [PATCH 2.6.11.5] atkbd: suppress debug output (was: printk with anti-cluttering-feature) Bodo Eggert

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=423D6353.5010603@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=7eggert@gmx.de \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.