From: Daniel Walker <dwalker@mvista.com>
To: James Morris <jmorris@namei.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
johnstul@us.ibm.com
Subject: Re: [PATCH 9/9] clocksource: refactor duplicate registration checking
Date: Fri, 30 Mar 2007 19:47:52 -0700 [thread overview]
Message-ID: <1175309273.12252.184.camel@imap.mvista.com> (raw)
In-Reply-To: <Line.LNX.4.64.0703302158380.29742@d.namei>
On Fri, 2007-03-30 at 21:59 -0400, James Morris wrote:
> On Fri, 30 Mar 2007, Daniel Walker wrote:
>
> > /**
> > * clocksource_register - Used to install new clocksources
> > * @t: clocksource to be registered
> > *
> > - * Returns -EBUSY if registration fails, zero otherwise.
> > + * Always returns zero.
> > */
> > int clocksource_register(struct clocksource *c)
>
> Return should be void, then.
Yeah, that's another patch tho ..
Daniel
prev parent reply other threads:[~2007-03-31 2:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 18:45 [PATCH 1/9] clocksource: arm initialize list value Daniel Walker
2007-03-30 18:45 ` [PATCH 2/9] clocksource: parisc " Daniel Walker
2007-03-30 18:45 ` [PATCH 3/9] clocksource: avr32 " Daniel Walker
2007-03-30 18:45 ` [PATCH 4/9] clocksource: mips " Daniel Walker
2007-03-30 18:45 ` [PATCH 5/9] clocksource: i386 " Daniel Walker
2007-03-30 18:45 ` [PATCH 6/9] clocksource: x86_64 " Daniel Walker
2007-03-30 18:45 ` [PATCH 7/9] clocksource: driver " Daniel Walker
2007-03-30 18:45 ` [PATCH 8/9] clocksource: s390 " Daniel Walker
2007-03-30 19:09 ` Heiko Carstens
2007-03-30 19:19 ` Daniel Walker
2007-03-30 19:36 ` Heiko Carstens
2007-03-30 18:45 ` [PATCH 9/9] clocksource: refactor duplicate registration checking Daniel Walker
2007-03-31 1:59 ` James Morris
2007-03-31 2:47 ` Daniel Walker [this message]
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=1175309273.12252.184.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=akpm@linux-foundation.org \
--cc=jmorris@namei.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.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®