From: Borislav Petkov <bp@alien8.de>
To: Tyler Hicks <tyhicks@linux.microsoft.com>
Cc: Lei Wang <lewan@microsoft.com>, Tony Luck <tony.luck@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sinan Kaya <okaya@kernel.org>,
Shiping Ji <shiping.linux@gmail.com>,
James Morse <james.morse@arm.com>,
Robert Richter <rric@kernel.org>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC/dmc520: Don't print an error for each unconfigured interrupt line
Date: Tue, 18 Jan 2022 18:28:16 +0100 [thread overview]
Message-ID: <Yeb4sK+ZmSHjWPWL@zn.tnic> (raw)
In-Reply-To: <20220118152816.GA89184@sequoia>
On Tue, Jan 18, 2022 at 09:28:16AM -0600, Tyler Hicks wrote:
> KERN_ERR messages trip log scanners and cause concern that the
> kernel/hardware is not configured or working correctly. They also add a
> little big of ongoing stress into kernel maintainer's lives, as we
> prepare and test kernel updates, since they show up as red text in
> journalctl output that we have to think about regularly. Multiple
> KERN_ERR messages, 8 in this case, can also be considered a little worse
> than a single error message.
It sounds to me like you wanna read
Documentation/process/stable-kernel-rules.rst
first.
> I feel like this trivial fix is worth taking into stable rather than
> suppressing these errors (mentally and in log scanners) for years.
Years?
In any case, sorry, no, I don't consider this stable material.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-01-18 17:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 16:38 Tyler Hicks
2022-01-12 17:19 ` Lei Wang (DPLAT)
2022-01-16 18:29 ` Borislav Petkov
2022-01-18 15:28 ` Tyler Hicks
2022-01-18 17:28 ` Borislav Petkov [this message]
2022-01-18 19:54 ` Tyler Hicks
2022-01-18 21:04 ` Borislav Petkov
2022-01-19 9:17 ` Greg Kroah-Hartman
2022-01-19 9:37 ` Borislav Petkov
2022-01-19 10:28 ` Greg Kroah-Hartman
2022-04-04 21:56 ` Tyler Hicks
2022-04-18 20:40 ` Tyler Hicks
2022-04-18 21:13 ` Borislav Petkov
2022-04-18 21:34 ` Tyler Hicks
2022-04-19 9:36 ` 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=Yeb4sK+ZmSHjWPWL@zn.tnic \
--to=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=lewan@microsoft.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=okaya@kernel.org \
--cc=rric@kernel.org \
--cc=shiping.linux@gmail.com \
--cc=tony.luck@intel.com \
--cc=tyhicks@linux.microsoft.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®