[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yeb4sK+ZmSHjWPWL@zn.tnic>
Date: Tue, 18 Jan 2022 18:28:16 +0100
From: Borislav Petkov <bp@...en8.de>
To: Tyler Hicks <tyhicks@...ux.microsoft.com>
Cc: Lei Wang <lewan@...rosoft.com>, Tony Luck <tony.luck@...el.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Sinan Kaya <okaya@...nel.org>,
Shiping Ji <shiping.linux@...il.com>,
James Morse <james.morse@....com>,
Robert Richter <rric@...nel.org>, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] EDAC/dmc520: Don't print an error for each unconfigured
interrupt line
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
Powered by blists - more mailing lists