From: Arjan van de Ven <arjan@infradead.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: tglx@linutronix.de, akpm@osdl.org, johnstul@us.ibm.com,
mingo@elte.hu, zippel@linux-m68k.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: + clocksource-initialize-list-value.patch added to -mm tree
Date: Sun, 08 Oct 2006 17:07:23 +0200 [thread overview]
Message-ID: <1160320043.3000.178.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1160318579.3693.8.camel@c-67-180-230-165.hsd1.ca.comcast.net>
On Sun, 2006-10-08 at 07:42 -0700, Daniel Walker wrote:
> On Sun, 2006-10-08 at 11:50 +0200, Thomas Gleixner wrote:
> > On Fri, 2006-10-06 at 18:53 -0700, akpm@osdl.org wrote:
> > > A change to clocksource initialization. It's optional for new clocksources,
> > > but prefered. If the list field is initialized it allows clocksource_register
> > > to complete faster since it doesn't have the scan the list of clocks doing
> > > strcmp on each.
> >
> > Either make it required or not.
>
> This is for compatability with all those clocksources people are writing
> that just haven't been released (assuming they will be eventually
> released). I would love to make this required.
so do it. The ones that are in development are easily fixed and
consistency is worth a LOT in terms of API. Bonus points if the kernel
printk's a helpful message on abuse.
next prev parent reply other threads:[~2006-10-08 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610070153.k971rsDf020869@shell0.pdx.osdl.net>
2006-10-08 9:50 ` Thomas Gleixner
2006-10-08 14:42 ` Daniel Walker
2006-10-08 15:07 ` Arjan van de Ven [this message]
2006-10-08 15:13 ` Daniel Walker
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=1160320043.3000.178.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®