From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 2/4] ARM: Allow machines to override __delay()
Date: Wed, 08 Dec 2010 13:07:59 -0800 [thread overview]
Message-ID: <1291842479.12568.39.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <4CFFEB00.5090807@codeaurora.org>
On Wed, 2010-12-08 at 12:30 -0800, Stephen Boyd wrote:
> On 12/08/2010 12:26 PM, Daniel Walker wrote:
> >
> > The last time I thought you said there was no size change ? My tests
> > showed a decrease ..
>
> Oh, right. There was no size change when I moved __delay() into the
> header in addition to the others.
So is there a problem with doing the inlining then ? If you get the same
size kernel, then that seems like a lateral move in your case.
Daniel
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-12-08 21:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 4:38 [PATCHv3 0/4] ARM: Fixing udelay() for SMP and non-SMP systems Stephen Boyd
2010-12-08 4:38 ` [PATCHv3 1/4] ARM: Translate delay.S into (mostly) C Stephen Boyd
2010-12-08 4:38 ` [PATCHv3 2/4] ARM: Allow machines to override __delay() Stephen Boyd
2010-12-08 19:22 ` Daniel Walker
2010-12-08 20:24 ` Stephen Boyd
2010-12-08 20:26 ` Daniel Walker
2010-12-08 20:30 ` Stephen Boyd
2010-12-08 21:07 ` Daniel Walker [this message]
2010-12-08 4:38 ` [PATCHv3 3/4] ARM: Implement a timer based __delay() loop Stephen Boyd
2010-12-08 4:38 ` [PATCHv3 4/4] msm: timer: Migrate to timer based __delay() Stephen Boyd
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=1291842479.12568.39.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).