linux-kernel - Re: [PATCH 3/7] microblaze: add parameter to microblaze

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 23 Apr 2009 14:38:45 +0200
From:	Michal Simek <michal.simek@...alogix.com>
To:	coly.li@...e.de
CC:	LKML <linux-kernel@...r.kernel.org>,
	Michal Simek <monstr@...str.eu>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH 3/7] microblaze: add parameter to microblaze_read()

Coly Li wrote:
> This patch modifies parameter of microblaze_read() from 'void' to 'struct
> clocksource *cs', which fixes compile warning for incompatible parameter type.
>
> Signed-off-by: Coly Li <coly.li@...e.de>
> Cc: Michal Simek <monstr@...str.eu>
> Cc: Ingo Molnar <mingo@...e.hu>
> ---
>  arch/microblaze/kernel/timer.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/microblaze/kernel/timer.c b/arch/microblaze/kernel/timer.c
> index 05a497e..bdfa2f9 100644
> --- a/arch/microblaze/kernel/timer.c
> +++ b/arch/microblaze/kernel/timer.c
> @@ -176,7 +176,7 @@ static __init void microblaze_clockevent_init(void)
>  	clockevents_register_device(&clockevent_microblaze_timer);
>  }
>
> -static cycle_t microblaze_read(void)
> +static cycle_t microblaze_read(struct clocksource *cs)
>  {
>  	/* reading actual value of timer 1 */
>  	return (cycle_t) (in_be32(TIMER_BASE + TCR1));
>
>   
Add to fixes-for-linus branch.

Michal

-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663

--
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/