18 May
2016
18 May
'16
6:21 p.m.
On Wed, May 18, 2016 at 05:50:50PM +0200, Alexander Stein wrote:
My first idea was to use dev_dbg() but that actualy remove that message at all, unless dynamic debug is used, so I went with dev_notice. It's still there, but does not clobber quiet boot log, nor some sophisticated kernel log parser as journalctl which prints errors in red color.
It's just shifting the problem around... it sounds like for your use case suppressing the messages until we finish kernel boot would deal with most of the issue in a far more general fashion.