From: Steven Rostedt <rostedt@goodmis.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [PATCH 2/3] clear_warn_once: bind a timer to written reset value
Date: Mon, 30 Nov 2020 22:36:47 -0500 [thread overview]
Message-ID: <20201130223647.71f8e621@oasis.local.home> (raw)
In-Reply-To: <20201130171759.GA26693@windriver.com>
On Mon, 30 Nov 2020 12:17:59 -0500
Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> > Anyway, would there ever be a need to have it cleared in less than 1 minute
> > intervals?
>
> I don't think so - as I said in another follow up from last week:
>
> https://lore.kernel.org/lkml/20201127174316.GA11748@windriver.com/
>
> I'd also indicated in the above that I'd be fine with adding a minimum
> of 1m if people feel better about that. Also maybe moving the units to
> minutes instead of seconds helps implicitly convey the intended use
> better -- i.e. "don't be smashing on this every second" -- maybe that
> was your point as well - and I'd agree with that.
That was my second point. That is, why would anyone care about a
resolution in seconds for this?
-- Steve
next prev parent reply other threads:[~2020-12-01 3:37 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 [this message]
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
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=20201130223647.71f8e621@oasis.local.home \
--to=rostedt@goodmis.org \
--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=sergey.senozhatsky@gmail.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
all inboxes | Powered by JetHome®