[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221107170127.i5bfkx45egaf2oh4@builder.lan>
Date: Mon, 7 Nov 2022 11:01:27 -0600
From: Bjorn Andersson <andersson@...nel.org>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: kernel test robot <lkp@...el.com>, Andy Gross <agross@...nel.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
kbuild-all@...ts.01.org,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Maulik Shah <quic_mkshah@...cinc.com>,
Rajendra Nayak <quic_rjendra@...cinc.com>,
Sudeep Holla <sudeep.holla@....com>,
Amit Pundir <amit.pundir@...aro.org>,
linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 6/6] soc: qcom: rpmh-rsc: Write CONTROL_TCS with next
timer wakeup
On Wed, Oct 19, 2022 at 01:47:17AM +0800, kernel test robot wrote:
[..]
> 155 #define USECS_TO_CYCLES(time_usecs) \
> 156 xloops_to_cycles((time_usecs) * 0x10C7UL)
> 157
> 158 static inline unsigned long xloops_to_cycles(unsigned long xloops)
Any objections to me changing the type to u64 while applying the
patches?
Regards,
Bjorn
> 159 {
> > 160 return (xloops * loops_per_jiffy * HZ) >> 32;
> 161 }
> 162
Powered by blists - more mailing lists