From: cdall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/kvm: fix misleading kconfig text for 16K pages
Date: Fri, 2 Jun 2017 15:18:30 +0200 [thread overview]
Message-ID: <20170602131830.GC397@cbox> (raw)
In-Reply-To: <1496401340-24802-1-git-send-email-mark.rutland@arm.com>
On Fri, Jun 02, 2017 at 12:02:20PM +0100, Mark Rutland wrote:
> We've supported KVM with 16K pages since commit:
>
> 02e0b7600f835007 ("arm64: kvm: Add support for 16K pages")
>
> ... yet the kconfig text says this combination is not supported.
>
> Let's fix that by deleting the misleading text.
>
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Acked-by: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Christoffer Dall <christoffer.dall@linaro.org>
> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
> Cc: kvmarm at lists.cs.columbia.edu
Acked-by: Christoffer Dall <cdall@linaro.org>
prev parent reply other threads:[~2017-06-02 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 11:02 [PATCH] arm64/kvm: fix misleading kconfig text for 16K pages Mark Rutland
2017-06-02 11:08 ` Suzuki K Poulose
2017-06-02 13:18 ` Christoffer Dall [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=20170602131830.GC397@cbox \
--to=cdall@linaro.org \
--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).