linux-kernel - Re: [PATCH 1/2] drivers/regulator/core.c: Don't print error on EPROBE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <54873B8E.1060106@topic.nl>
Date:	Tue, 09 Dec 2014 19:12:30 +0100
From:	Mike Looijmans <mike.looijmans@...ic.nl>
To:	Mark Brown <broonie@...nel.org>
CC:	lgirdwood@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] drivers/regulator/core.c: Don't print error on EPROBE_DEFER

On 12/09/2014 05:14 PM, Mark Brown wrote:
>>If a regulator depends on another regulator that happens to be called
>>later, the kernel always prints a message like this:
>>   reg-fixed-voltage regulator_sd1: Failed to find supply vin
>>Since the deferral is not something fatal, nor even something the user
>>may need to be aware about, reduce the message to debug level.

Can we instead at least reduce it to WARN or INFO level then?

I have to explain over and over again that there's no problem when that 
message comes along ten times in a row. And it causes people to overlook 
the messages that really are errors.

-- 
Mike Looijmans
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/