linux-kernel - Re: [PATCH 08/19] OpenRISC: Timekeeping

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 for Android: free password hash cracker in your pocket

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

Message-Id: <201106192106.19667.arnd@arndb.de>
Date:	Sun, 19 Jun 2011 21:06:19 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Jonas Bonn <jonas@...thpole.se>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/19] OpenRISC: Timekeeping

> + arch/openrisc/kernel/time.c       |  182 +++++++++++++++++++++++++++++++++++++

Would this fit into drivers/clocksource, at least partly?

> +static struct clocksource openrisc_timer = {
> +	.name		= "openrisc_timer",
> +        .rating         = 200,
> +	.read		= openrisc_timer_read,
> +        .mask           = CLOCKSOURCE_MASK(32),
> +        .flags          = CLOCK_SOURCE_IS_CONTINUOUS,
> +};
> +
> +static int __init openrisc_timer_init(void)
> +{
> +        if (clocksource_register_hz(&openrisc_timer, cpuinfo.clock_frequency))
> +                panic("failed to register clocksource");
> +
> +	/* Enable the incrementer: 'continuous' mode with interrupt disabled */
> +        mtspr(SPR_TTMR, SPR_TTMR_CR);
> +
> +        return 0;
> +}

You have soem whitespace damage here. It would be good to run your patches
through scripts/checkpatch.pl and fix up everything reported there.



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