| 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
| ||
|
Date: Wed, 8 Oct 2014 15:59:12 -0700 From: Guenter Roeck <linux@...ck-us.net> To: Mark Brown <broonie@...nel.org> Cc: Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org, linaro-kernel@...ts.linaro.org, atull@...nsource.altera.com Subject: Re: [PATCH] regulator: of: Lower the severity of the error with no container On Wed, Oct 08, 2014 at 11:36:01PM +0100, Mark Brown wrote: > On Wed, Oct 08, 2014 at 03:34:03PM -0700, Guenter Roeck wrote: > > > Would it also be possible to lower the severity of the "no parameters" > > message ? > > Could you be more specific please? There is a log message "no parameters" for each regulator. This is printed unconditionally from print_constraints(). Looking through the code again, looks like this is on purpose. It is just a bit annoying to get lots of those messages. One of the systems I am dealing with has 17 LTC2978 chips in it, with 8 channels each. That results in 136 times "no parameters" in the boot log. And that is not even a fully populated system; if fully populated, there can be more than 60 of those chips. 500+ lines of similar log messages is really a bit on the high side. It might help if there was a way to silence the messages, ie to make "print_constraints" optional. Thanks, Guenter -- 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/
Powered by blists - more mailing lists