From: colin.tuckley@arm.com (Colin Tuckley)
To: linux-arm-kernel@lists.infradead.org
Subject: realview compulsory enables CONFIG_ARM_PATCH_PHYS_VIRT on me
Date: Tue, 6 Dec 2011 08:29:43 -0000 [thread overview]
Message-ID: <000101ccb3f1$34cbbf40$9e633dc0$@tuckley@arm.com> (raw)
In-Reply-To: <20111205233621.GH14542@n2100.arm.linux.org.uk>
> -----Original Message-----
> depends on !ARCH_REALVIEW || !SPARSEMEM
> No, it's correct. None of you are understanding the logic.
> And this clearly shows that if we have realview _and_ sparsemem
> enabled,
> then we don't want P2V patching in place.
In which case wouldn't it be clearer if it was written as:
depends on !(ARCH_REALVIEW && SPARSEMEM)
Colin
next prev parent reply other threads:[~2011-12-06 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 21:22 realview compulsory enables CONFIG_ARM_PATCH_PHYS_VIRT on me Linus Walleij
2011-12-05 21:57 ` Rob Herring
2011-12-05 22:08 ` Nicolas Pitre
2011-12-05 23:36 ` Russell King - ARM Linux
2011-12-06 0:37 ` Nicolas Pitre
2011-12-06 0:46 ` Russell King - ARM Linux
2011-12-06 8:29 ` Colin Tuckley [this message]
2011-12-06 10:30 ` Linus Walleij
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='000101ccb3f1$34cbbf40$9e633dc0$@tuckley@arm.com' \
--to=colin.tuckley@arm.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;
as well as URLs for NNTP newsgroup(s).