From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v3] 6/7] watchdog: Remove ARCH_KIRKWOOD dependency
Date: Sat, 30 Aug 2014 18:46:11 +0200 [thread overview]
Message-ID: <1409417172-6846-7-git-send-email-andrew@lunn.ch> (raw)
In-Reply-To: <1409417172-6846-1-git-send-email-andrew@lunn.ch>
mach-kirkwood has been removed, now that kirkwood lives in mach-mvebu.
ARCH_MVEBU is sufficient.
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Cc: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog at vger.kernel.org
---
drivers/watchdog/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
index f57312fced80..1d1330a78af3 100644
--- a/drivers/watchdog/Kconfig
+++ b/drivers/watchdog/Kconfig
@@ -301,7 +301,7 @@ config DAVINCI_WATCHDOG
config ORION_WATCHDOG
tristate "Orion watchdog"
- depends on ARCH_ORION5X || ARCH_KIRKWOOD || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU
+ depends on ARCH_ORION5X || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU
select WATCHDOG_CORE
help
Say Y here if to include support for the watchdog timer
--
2.1.0
next prev parent reply other threads:[~2014-08-30 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 16:46 [Patch v3] 0/7] Remove mach-kirkwood Andrew Lunn
2014-08-30 16:46 ` [Patch v3] 1/7] cpuidle: kirkwood: Remove ARCH_KIRKWOOD dependency Andrew Lunn
2014-09-03 13:45 ` Daniel Lezcano
2014-08-30 16:46 ` [Patch v3] 2/7] ata: " Andrew Lunn
2014-08-31 11:02 ` Tejun Heo
2014-08-30 16:46 ` [Patch v3] 3/7] thermal: " Andrew Lunn
2014-09-02 11:53 ` edubezval at gmail.com
2014-08-30 16:46 ` [Patch v3] 4/7] leds: " Andrew Lunn
2014-08-30 16:46 ` [Patch v3] 5/7] rtc: " Andrew Lunn
2014-08-30 16:46 ` Andrew Lunn [this message]
2014-08-30 16:46 ` [Patch v3] 7/7] cpufreq: " Andrew Lunn
2014-09-01 4:05 ` Viresh Kumar
2014-09-01 13:56 ` [Patch v3] 0/7] Remove mach-kirkwood Rafael J. Wysocki
2014-09-01 14:03 ` Andrew Lunn
2014-09-01 23:46 ` Rafael J. Wysocki
2014-09-09 15:10 ` Jason Cooper
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=1409417172-6846-7-git-send-email-andrew@lunn.ch \
--to=andrew@lunn.ch \
--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).