From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 1/2] clocksource: fix type confusion for clocksource_mmio_readX_Y
Date: Mon, 19 May 2014 11:09:27 +0200 [thread overview]
Message-ID: <5379CA47.4020900@linaro.org> (raw)
In-Reply-To: <7dd1dc731dd24e15a170ef95aeee2a2e@BY2PR03MB505.namprd03.prod.outlook.com>
On 05/19/2014 04:35 AM, Li.Xiubo@freescale.com wrote:
> Hi,
>
> I'd like to know the status about this patch series...
> :)
I think the patches are ok. I have them in my queue for 3.16.
>> -----Original Message-----
>> From: Xiubo Li [mailto:Li.Xiubo@freescale.com]
>> Sent: Wednesday, April 23, 2014 10:12 AM
>> To: daniel.lezcano@linaro.org; tglx@linutronix.de; linux-
>> kernel@vger.kernel.org
>> Cc: Xiubo Li-B47053
>> Subject: [PATCHv2 1/2] clocksource: fix type confusion for
>> clocksource_mmio_readX_Y
>>
>> The types' definations are:
>> o cycle_t -> u64
>> o readl_relaxed -> u32
>> o readw_relaxed -> u16
>>
>> So let clocksource_mmio_readX_Ys return a cast to cycle_t, though
>> this maybe look reduntant sometimes, it make sense and they will be
>> more readable and less confusion...
>>
>> This patch clarifies the functions type and fix it.
>>
>> Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
>> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
>> ---
>> drivers/clocksource/mmio.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/clocksource/mmio.c b/drivers/clocksource/mmio.c
>> index c0e2512..19a6b3f 100644
>> --- a/drivers/clocksource/mmio.c
>> +++ b/drivers/clocksource/mmio.c
>> @@ -22,22 +22,22 @@ static inline struct clocksource_mmio
>> *to_mmio_clksrc(struct clocksource *c)
>>
>> cycle_t clocksource_mmio_readl_up(struct clocksource *c)
>> {
>> - return readl_relaxed(to_mmio_clksrc(c)->reg);
>> + return (cycle_t)readl_relaxed(to_mmio_clksrc(c)->reg);
>> }
>>
>> cycle_t clocksource_mmio_readl_down(struct clocksource *c)
>> {
>> - return ~readl_relaxed(to_mmio_clksrc(c)->reg);
>> + return ~(cycle_t)readl_relaxed(to_mmio_clksrc(c)->reg);
>> }
>>
>> cycle_t clocksource_mmio_readw_up(struct clocksource *c)
>> {
>> - return readw_relaxed(to_mmio_clksrc(c)->reg);
>> + return (cycle_t)readw_relaxed(to_mmio_clksrc(c)->reg);
>> }
>>
>> cycle_t clocksource_mmio_readw_down(struct clocksource *c)
>> {
>> - return ~(unsigned)readw_relaxed(to_mmio_clksrc(c)->reg);
>> + return ~(cycle_t)readw_relaxed(to_mmio_clksrc(c)->reg);
>> }
>>
>> /**
>> --
>> 1.8.4
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2014-05-19 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 2:11 [PATCHv2 1/2] clocksource: fix type confusion for clocksource_mmio_readX_Y Xiubo Li
2014-04-23 2:12 ` [PATCHv2 2/2] clocksource: fix clocksource_mmio_readX_down Xiubo Li
2014-05-19 2:35 ` [PATCHv2 1/2] clocksource: fix type confusion for clocksource_mmio_readX_Y Li.Xiubo
2014-05-19 9:09 ` Daniel Lezcano [this message]
2014-05-19 9:12 ` Li.Xiubo
2014-05-19 14:19 ` Daniel Lezcano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5379CA47.4020900@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Li.Xiubo@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.