All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: johnstul@us.ibm.com, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] generic clocksource updates
Date: Thu, 06 Apr 2006 12:06:11 +0200	[thread overview]
Message-ID: <1144317972.5344.681.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0604032155070.4707@scrub.home>

On Mon, 2006-04-03 at 21:55 +0200, Roman Zippel wrote:
>  struct clocksource {
>  	char *name;
> @@ -58,11 +57,11 @@ struct clocksource {
>  	u32 mult;
>  	u32 shift;
>  	int (*update_callback)(void);
> -	int is_continuous;

This field was introduced to have a clear property description. The
rating field might be used for this, but from a given rating on a
particular CPU architecture it might be hard to deduce whether this
clock source is good enough so we can switch to high resolution timer
mode.

is_continous is maybe not the best choice, but a flag field to retrieve
certain properties would be a good thing to have.

	tglx





  reply	other threads:[~2006-04-06 10:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03 19:55 [PATCH 1/5] generic clocksource updates Roman Zippel
2006-04-06 10:06 ` Thomas Gleixner [this message]
2006-04-06 19:00   ` Roman Zippel
2006-04-06 19:32     ` Thomas Gleixner
2006-04-07 20:43       ` Roman Zippel
2006-04-07 21:08         ` john stultz
2006-04-07 22:40         ` Thomas Gleixner
2006-04-12 11:16           ` Roman Zippel
2006-04-07 18:38 ` john stultz
2006-04-27 20:41   ` Roman Zippel
2006-05-06  2:27     ` john stultz

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=1144317972.5344.681.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@osdl.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.org \
    /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.