From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Marco Elver <elver@google.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Potapenko <glider@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Wei Liu <wei.liu@kernel.org>, Mike Rapoport <rppt@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
John Ogness <john.ogness@linutronix.de>,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
Alexander Popov <alex.popov@linux.com>
Subject: Re: [PATCH] panic: use error_report_end tracepoint on warnings
Date: Mon, 15 Nov 2021 16:38:35 +0200 [thread overview]
Message-ID: <YZJw69RdPES7gHBM@smile.fi.intel.com> (raw)
In-Reply-To: <20211115085630.1756817-1-elver@google.com>
On Mon, Nov 15, 2021 at 09:56:30AM +0100, Marco Elver wrote:
> Introduce the error detector "warning" to the error_report event and use
> the error_report_end tracepoint at the end of a warning report.
>
> This allows in-kernel tests but also userspace to more easily determine
> if a warning occurred without polling kernel logs.
...
> enum error_detector {
> ERROR_DETECTOR_KFENCE,
> - ERROR_DETECTOR_KASAN
> + ERROR_DETECTOR_KASAN,
> + ERROR_DETECTOR_WARN
...which exactly shows my point (given many times somewhere else) why comma
is good to have when we are not sure the item is a terminator one in the enum
or array of elements.
> };
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-11-15 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 8:56 Marco Elver
2021-11-15 14:38 ` Andy Shevchenko [this message]
2021-11-15 14:40 ` Marco Elver
2021-11-15 14:55 ` Andy Shevchenko
2021-12-10 23:35 ` Steven Rostedt
2021-12-10 23:38 ` Marco Elver
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=YZJw69RdPES7gHBM@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alex.popov@linux.com \
--cc=arnd@arndb.de \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=john.ogness@linutronix.de \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=wei.liu@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 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®