From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: omap1: fix build when !CONFIG_OMAP_32K_TIMER
Date: Thu, 13 Feb 2014 14:52:27 -0800 [thread overview]
Message-ID: <20140213225226.GE28216@atomide.com> (raw)
In-Reply-To: <1389636237-2998-1-git-send-email-balbi@ti.com>
* Felipe Balbi <balbi@ti.com> [140113 10:06]:
> If CONFIG_OMAP_32K_TIMER isn't enabled, we will
> try to use enable_dyn_sleep which wasn't defined
> anywhere.
>
> In order to fix the problem, we always define
> enable_dyn_sleep as 0 when !CONFIG_OMAP_32K_TIMER.
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
Thanks applying into omap-for-v3.14/fixes.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap1: fix build when !CONFIG_OMAP_32K_TIMER
Date: Thu, 13 Feb 2014 14:52:27 -0800 [thread overview]
Message-ID: <20140213225226.GE28216@atomide.com> (raw)
In-Reply-To: <1389636237-2998-1-git-send-email-balbi@ti.com>
* Felipe Balbi <balbi@ti.com> [140113 10:06]:
> If CONFIG_OMAP_32K_TIMER isn't enabled, we will
> try to use enable_dyn_sleep which wasn't defined
> anywhere.
>
> In order to fix the problem, we always define
> enable_dyn_sleep as 0 when !CONFIG_OMAP_32K_TIMER.
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
Thanks applying into omap-for-v3.14/fixes.
Tony
next prev parent reply other threads:[~2014-02-13 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 18:03 [PATCH] arm: omap1: fix build when !CONFIG_OMAP_32K_TIMER Felipe Balbi
2014-01-13 18:03 ` Felipe Balbi
2014-02-13 22:52 ` Tony Lindgren [this message]
2014-02-13 22:52 ` Tony Lindgren
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=20140213225226.GE28216@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.