From: Zumeng Chen <zumeng.chen@windriver.com>
To: <shubhrajyoti@ti.com>, <hvaibhav@ti.com>, <wim@iguana.be>
Cc: <linux-watchdog@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<paul.gortmaker@windriver.com>, <tony@atomide.com>
Subject: [PATCH v2 2/3] Watchdog: Omap: select watchdog core for framework change
Date: Mon, 9 Jul 2012 15:35:27 +0800 [thread overview]
Message-ID: <1341819328-3514-3-git-send-email-zumeng.chen@windriver.com> (raw)
In-Reply-To: <1341819328-3514-1-git-send-email-zumeng.chen@windriver.com>
Since the current watchdog framework depends on the watchdog core
so select it in Kconfig.
Signed-off-by: Zumeng Chen <zumeng.chen@windriver.com>
---
drivers/watchdog/Kconfig | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
index fe819b7..fb5b108 100644
--- a/drivers/watchdog/Kconfig
+++ b/drivers/watchdog/Kconfig
@@ -232,6 +232,7 @@ config EP93XX_WATCHDOG
config OMAP_WATCHDOG
tristate "OMAP Watchdog"
depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
+ select WATCHDOG_CORE
help
Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
--
1.7.5.4
next prev parent reply other threads:[~2012-07-09 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 7:35 [PATCH v2 RESEND 0/3] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework Zumeng Chen
2012-07-09 7:35 ` [PATCH v2 1/3] Watchdog: Omap: Changes for the new " Zumeng Chen
2012-07-09 7:35 ` Zumeng Chen [this message]
2012-07-09 7:35 ` [PATCH v2 3/3] Watchdog: Omap: get the bootstatus for OMAP2Plus Zumeng Chen
2012-07-10 4:17 ` [PATCH v2 RESEND 0/3] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework Zumeng Chen
2012-07-11 8:10 ` Zumeng Chen
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=1341819328-3514-3-git-send-email-zumeng.chen@windriver.com \
--to=zumeng.chen@windriver.com \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=shubhrajyoti@ti.com \
--cc=tony@atomide.com \
--cc=wim@iguana.be \
/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).