From: Philippe De Muyter <phdm@macqel.be>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] watchdog,m68knommu: allow M548x watchdog compilation only for M548x
Date: Mon, 10 Jan 2011 13:27:35 +0100 [thread overview]
Message-ID: <20110110122735.GA23114@frolo.macqel> (raw)
In-Reply-To: <20110110072750.GL3801@infomag.iguana.be>
Hi Wim and Stephen,
On Mon, Jan 10, 2011 at 08:27:50AM +0100, Wim Van Sebroeck wrote:
> Hi Stephen,
>
> > After merging the watchdog tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
>
> This driver is for the m68K architecture. I apparently missed checking
> the dependancy in Kconfig. I'll fix it today.
Here is my attempt :
allow M548x watchdog compilation only for M548x
Signed-off-by: Philippe De Muyter <phdm@macqel.be>
---
drivers/watchdog/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
index b742f8b..d54bea0 100644
--- a/drivers/watchdog/Kconfig
+++ b/drivers/watchdog/Kconfig
@@ -831,7 +831,7 @@ config SBC_EPX_C3_WATCHDOG
config M548x_WATCHDOG
tristate "MCF548x watchdog support"
- depends on WATCHDOG
+ depends on M548x
help
To compile this driver as a module, choose M here: the
module will be called m548x_wdt.
--
1.7.1
prev parent reply other threads:[~2011-01-10 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 3:12 linux-next: build failure after merge of the watchdog tree Stephen Rothwell
2011-01-10 7:27 ` Wim Van Sebroeck
2011-01-10 12:27 ` Philippe De Muyter [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=20110110122735.GA23114@frolo.macqel \
--to=phdm@macqel.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).