[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b040c32a0812230929u282f0f2bn9221bf2e176d82eb@mail.gmail.com>
Date: Tue, 23 Dec 2008 09:29:52 -0800
From: Ken Chen <kenchen@...gle.com>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
sparclinux <sparclinux@...r.kernel.org>, mingo@...e.hu,
sfr@...b.auug.org.au, linux-kernel@...r.kernel.org,
paulus@...ba.org, tglx@...utronix.de, hpa@...or.com,
linux-next@...r.kernel.org
Subject: Re: [PATCH] sparc64: use unsigned long long for u64
On Tue, Dec 23, 2008 at 9:26 AM, Sam Ravnborg <sam@...nborg.org> wrote:
>> wait, why does this need to be changed?
>
> We have:
> clocksource_tick.read = tick_ops->get_tick;
>
> And clocksource_tick is of type clocksource:
>
> struct clocksource {
> ...
> cycle_t (*read)(void);
>
> And cycle_t is:
> /* clocksource cycle base type */
> typedef u64 cycle_t;
>
> And u64 is now:
> unsigned long long - thus we need to fix prototype
> of get_tick to fix the warnings.
>
> A cast could do it - but fixing the real problem
> is better here.
Sounds good to me. It was just a question. Thank you for the explanation.
- Ken
--
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