From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [PATCH 0/3] clear_warn_once: add timed interval resetting
Date: Mon, 30 Nov 2020 15:02:45 +0900 [thread overview]
Message-ID: <X8SLBcONiM5bQt4x@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <X8ElwBh9tw+OLHF+@alley>
On (20/11/27 17:13), Petr Mladek wrote:
>
> + Move clear_warn_once from debugfs to a location that is always
> available. For example, into /proc
Or a printk module param, which user-space can write to from crontab?
Hmm, but this has potential of becoming another /proc/sys/vm/drop_caches
though.
-ss
next prev parent reply other threads:[~2020-11-30 6:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 6:30 [PATCH 0/3] clear_warn_once: add timed interval resetting Paul Gortmaker
2020-11-26 6:30 ` [PATCH 1/3] clear_warn_once: expand debugfs to include read support Paul Gortmaker
2020-11-26 6:30 ` [PATCH 2/3] clear_warn_once: bind a timer to written reset value Paul Gortmaker
2020-11-30 16:20 ` Steven Rostedt
2020-11-30 17:17 ` Paul Gortmaker
2020-12-01 3:36 ` Steven Rostedt
2020-11-26 6:30 ` [PATCH 3/3] clear_warn_once: add a warn_once_reset= boot parameter Paul Gortmaker
2020-11-27 16:13 ` [PATCH 0/3] clear_warn_once: add timed interval resetting Petr Mladek
2020-11-27 17:43 ` Paul Gortmaker
2020-12-01 12:59 ` Petr Mladek
2020-11-30 6:02 ` Sergey Senozhatsky [this message]
2020-11-30 16:24 ` Steven Rostedt
2020-11-30 3:08 ` Andi Kleen
2020-11-30 17:38 ` Paul Gortmaker
2020-12-01 12:49 ` Petr Mladek
2020-12-01 18:05 ` Paul Gortmaker
2020-12-09 16:37 ` Petr Mladek
2020-12-09 17:21 ` Paul Gortmaker
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=X8SLBcONiM5bQt4x@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=ak@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).