From: David Daney <ddaney@caviumnetworks.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org,
Mikael Pettersson <mikpe@it.uu.se>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] Make MIPS dynamic clocksource/clockevent clock code generic
Date: Tue, 20 Oct 2009 14:56:53 -0700 [thread overview]
Message-ID: <4ADE3225.5050001@caviumnetworks.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0910200454300.2863@localhost.localdomain>
Thomas Gleixner wrote:
> On Sun, 18 Oct 2009, Linus Walleij wrote:
>> This moves the clocksource_set_clock() and clockevent_set_clock()
>> from the MIPS timer code into clockchips and clocksource where
>> it belongs. The patch was triggered by code posted by Mikael
>> Pettersson duplicating this code for the IOP ARM system. The
>> function signatures where altered slightly to fit into their
>> destination header files, unsigned int changed to u32 and inlined.
>>
>> Signed-off-by: Linus Walleij <linus.walleij@stericsson.com>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Mikael Pettersson <mikpe@it.uu.se>
>> Cc: Ralf Baechle <ralf@linux-mips.org>
>> ---
>> Ralf has stated in earlier conversation that this should be moved,
>> now we risk duplicating code so let's move it.
>
> Please do not make that functions inline. They are too large and there
> is no benefit of inlining them.
>
If that is the case, then perhaps they should not be defined in a header
file.
IMHO if you are defining a function in a header file it should always be
'static inline'. If you don't want it in-lined, put it in some
library so we only pick up a single instance of it.
David Daney
next prev parent reply other threads:[~2009-10-20 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 22:48 [PATCH] Make MIPS dynamic clocksource/clockevent clock code generic Linus Walleij
2009-10-18 22:10 ` Mikael Pettersson
[not found] ` <b2b2f2320910182217m31ce0a96g4912eeb9bea5f817@mail.gmail.com>
2009-10-19 5:22 ` Shane McDonald
2009-10-20 2:25 ` Ralf Baechle
2009-10-20 3:50 ` Thomas Gleixner
2009-10-20 8:19 ` Mikael Pettersson
2009-10-20 21:27 ` Linus Walleij
2009-10-20 21:56 ` David Daney [this message]
2009-10-20 22:16 ` Linus Walleij
2009-10-20 22:44 ` David Daney
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=4ADE3225.5050001@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mikpe@it.uu.se \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
/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