From: mark.langsdorf@calxeda.com (Mark Langsdorf)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mailbox: prevent pl320-ipc code from breaking none-AMBA systems
Date: Tue, 29 Jan 2013 10:36:53 -0600 [thread overview]
Message-ID: <1359477413-27881-1-git-send-email-mark.langsdorf@calxeda.com> (raw)
The pl320-ipc code depends on ARM AMBA, and should have the dependency
in its Kconfig.
Signed-off-by: Mark Langsdorf <mark.langsdorf@calxeda.com>
---
drivers/mailbox/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mailbox/Kconfig b/drivers/mailbox/Kconfig
index 9489554..9545c9f 100644
--- a/drivers/mailbox/Kconfig
+++ b/drivers/mailbox/Kconfig
@@ -8,6 +8,7 @@ menuconfig MAILBOX
if MAILBOX
config PL320_MBOX
bool "ARM PL320 Mailbox"
+ depends on ARM_AMBA
help
An implementation of the ARM PL320 Interprocessor Communication
Mailbox (IPCM), tailored for the Calxeda Highbank. It is used to
--
1.7.11.7
next reply other threads:[~2013-01-29 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 16:36 Mark Langsdorf [this message]
2013-01-29 21:55 ` [PATCH] mailbox: prevent pl320-ipc code from breaking none-AMBA systems Rafael J. Wysocki
2013-01-29 22:13 ` Mark Langsdorf
2013-01-29 23:11 ` Rafael J. Wysocki
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=1359477413-27881-1-git-send-email-mark.langsdorf@calxeda.com \
--to=mark.langsdorf@calxeda.com \
--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