Re: [PATCH 2/3] rtc: __rtc_read_time: reduce log level

2015-04-01 Thread Alexandre Belloni
On 31/03/2015 at 20:25:19 -0700, Joe Perches wrote : > On Wed, 2015-04-01 at 05:21 +0200, Alexandre Belloni wrote: > > On 28/03/2015 at 23:09:35 +0200, Aaro Koskinen wrote : > > > __rtc_read_time logs should be debug logs instead of error logs. > > > > > > For example, when the RTC clock is not se

Re: [PATCH 2/3] rtc: __rtc_read_time: reduce log level

2015-03-31 Thread Joe Perches
On Wed, 2015-04-01 at 05:21 +0200, Alexandre Belloni wrote: > On 28/03/2015 at 23:09:35 +0200, Aaro Koskinen wrote : > > __rtc_read_time logs should be debug logs instead of error logs. > > > > For example, when the RTC clock is not set, it's not really useful > > to print a kernel error log every

Re: [PATCH 2/3] rtc: __rtc_read_time: reduce log level

2015-03-31 Thread Alexandre Belloni
On 28/03/2015 at 23:09:35 +0200, Aaro Koskinen wrote : > __rtc_read_time logs should be debug logs instead of error logs. > > For example, when the RTC clock is not set, it's not really useful > to print a kernel error log every time someone tries to read the clock: > > ~ # hwclock -r >

[PATCH 2/3] rtc: __rtc_read_time: reduce log level

2015-03-28 Thread Aaro Koskinen
__rtc_read_time logs should be debug logs instead of error logs. For example, when the RTC clock is not set, it's not really useful to print a kernel error log every time someone tries to read the clock: ~ # hwclock -r [ 604.508263] rtc rtc0: read_time: fail to read hwclo