From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [patch 2.6.21-rc4-omap1] omap2/pm.c build fix
Date: Thu, 29 Mar 2007 16:29:13 -0400 [thread overview]
Message-ID: <20070329202912.GM3638@atomide.com> (raw)
In-Reply-To: <200703281316.09088.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [070328 17:24]:
> Fix build bug ... next_timer_interrupt() depends on NO_IDLE_HZ
> or else (new style) NO_HZ, so don't assume it's always present.
>
> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
>
> --- a/arch/arm/mach-omap2/pm.c
> +++ b/arch/arm/mach-omap2/pm.c
> @@ -389,8 +389,12 @@ #endif
> }
>
> if (!resume)
> +#if defined(CONFIG_NO_IDLE_HZ) || defined(CONFIG_NO_HZ)
> printk("--- Going to %s %s (next timer after %u ms)\n", s1, s2,
> jiffies_to_msecs(next_timer_interrupt() - jiffies));
> +#else
> + printk("--- Going to %s %s\n", s1, s2);
> +#endif
> else
> printk("--- Woke up (slept for %u.%03u ms)\n", us / 1000, us % 1000);
> for (i = 0; i < reg_count; i++)
Pushing today.
Tony
prev parent reply other threads:[~2007-03-29 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 20:16 [patch 2.6.21-rc4-omap1] omap2/pm.c build fix David Brownell
2007-03-29 20:29 ` Tony Lindgren [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=20070329202912.GM3638@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
/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