From: Rafał Miłecki
Printing with pr_* functions requires adding line break manually.
Signed-off-by: Rafał Miłecki
---
Hi,
I think this change is so trivial it's not worth splitting per single
driver. Are you OK with that?
---
drivers/clocksource/arc_timer.c | 14 +++---
dri
,Thomas Gleixner ,Ingo Molnar
,Chris Zankel ,Max Filippov
,Arnd Bergmann
,x...@kernel.org,linux-al...@vger.kernel.org,linux-snps-arc@lists.infradead.org,linux-arm-ker...@lists.infradead.org,linux-hexa...@vger.kernel.org,linux-i...@vger.kernel.org,linux-m...@linux-mips.org,openr...@lists.librecor
Hi Vineet,
On Wed, 2017-02-22 at 10:49 -0800, Vineet Gupta wrote:
> On 02/22/2017 02:36 AM, Vlad Zakharov wrote:
> > We were reading clock rate directly from device tree "clock-frequency"
> > property of corresponding clock node in show_cpuinfo function.
> >
> > Such approach is correct only in c
On 03/09/2017 11:33 AM, Vlad Zakharov wrote:
>
>> And while we are at it - one of my wish list has been to print the core clk
>> in
>> early boot - i.e. in setup_processor()->arc_cpu_mumbojumbo() call path which
>> is
>> different from the other case u fixed. Any ideas how to do that - clk
>> fr