From: "SL Baur" <steve@xemacs.org>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Pavel Machek" <pavel@ucw.cz>,
"kernel list" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: gart: factor out common code
Date: Thu, 17 Apr 2008 00:34:03 -0700 [thread overview]
Message-ID: <ed10ee420804170034g73906d04s22a53f4ef3ef495f@mail.gmail.com> (raw)
In-Reply-To: <4806EE5F.1040305@firstfloor.org>
On 4/16/08, Andi Kleen <andi@firstfloor.org> wrote:
> SL Baur wrote:
> I think the casts make it more clear because the register is 32bit.
> The only truly ugly bit is naming a variable "tmp".
Good point.
> > that function is too big to be inlined so you should probably drop the explicit
> > `inline' and let the compiler decide.
> In a header static inline is needed, otherwise the compiler will warn
> about an unused static if it's not used which is unfortunate because
> not every includer wants to use all functions.
>
> That said the function should probably not be in a header.
Yes. Agreed. I'm happy enough having common duplicated
code removed, but I know Ingo is picky about saving space
whenever he can, so I thought I would point it out now before
it becomes a maintenance issue.
Thanks for the feedback. I'll focus harder on future reviews.
-sb
next prev parent reply other threads:[~2008-04-17 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 10:43 Pavel Machek
2008-04-15 23:25 ` SL Baur
2008-04-16 8:14 ` Pavel Machek
2008-04-17 2:55 ` SL Baur
2008-04-17 6:29 ` Andi Kleen
2008-04-17 7:34 ` SL Baur [this message]
2008-04-16 13:08 ` Ingo Molnar
2008-04-16 22:50 ` Yinghai Lu
2008-04-16 22:56 ` Pavel Machek
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=ed10ee420804170034g73906d04s22a53f4ef3ef495f@mail.gmail.com \
--to=steve@xemacs.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
/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®