From: Tony Wu <tung7970@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: [PATCH] MIPS: Fix MIPS32_COMPAT recursive dependency
Date: Tue, 13 Jan 2015 23:05:02 +0800 [thread overview]
Message-ID: <20150113230344-tung7970@googlemail.com> (raw)
Commit f92b81f16 (MIPS: Compat: Fix build error if CONFIG_MIPS32_COMPAT
but no compat ABI.) introduced a recursive dependency on MIPS32_COMPAT,
shown as follows:
arch/mips/Kconfig:2681:error: recursive dependency detected!
arch/mips/Kconfig:2681: symbol MIPS32_N32 depends on MIPS32_COMPAT
arch/mips/Kconfig:2658: symbol MIPS32_COMPAT is selected by MIPS32_N32
Signed-off-by: Tony Wu <tung7970@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 73983e1..33c0b88 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -2680,7 +2680,6 @@ config MIPS32_O32
config MIPS32_N32
bool "Kernel support for n32 binaries"
- depends on MIPS32_COMPAT
select COMPAT
select MIPS32_COMPAT
select SYSVIPC_COMPAT if SYSVIPC
next reply other threads:[~2015-01-13 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 15:05 Tony Wu [this message]
2015-01-14 11:40 ` [PATCH] MIPS: Fix MIPS32_COMPAT recursive dependency Ralf Baechle
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=20150113230344-tung7970@googlemail.com \
--to=tung7970@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.