[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5399EA29.7090302@codeaurora.org>
Date: Thu, 12 Jun 2014 10:58:01 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: "Li.Xiubo@...escale.com" <Li.Xiubo@...escale.com>
CC: Marc Zyngier <Marc.Zyngier@....com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] clocksource: arch_arm_timer: Fix timecounter initialization
On 06/12/14 00:45, Li.Xiubo@...escale.com wrote:
>
> And if so, why not just set it to 0 ? And by the way, 0 is must here ?
>
>
I would just set it to 0 and be done with it. But all of this doesn't
seem very urgent. The only user of this timecounter is using it for the
read() and mult/shift members. We never call timecounter_read() or
timecounter_cyc2time() so the nsec member is irrelevant.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
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