From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [kernel] KVM: PPC: Fix compile when CONFIG_PPC_RADIX_MMU is not defined
Date: Thu, 24 Jan 2019 14:40:29 +1100 (AEDT) [thread overview]
Message-ID: <43lSbd5fT5z9sMr@ozlabs.org> (raw)
In-Reply-To: <20190114003849.130240-1-aik@ozlabs.ru>
On Mon, 2019-01-14 at 00:38:49 UTC, Alexey Kardashevskiy wrote:
> This adds some stubs for hash only configs.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/cd6b8a631c5de3a6b7c8ef30337fd02b
cheers
prev parent reply other threads:[~2019-01-24 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 0:38 [PATCH kernel] KVM: PPC: Fix compile when CONFIG_PPC_RADIX_MMU is not defined Alexey Kardashevskiy
2019-01-24 3:40 ` Michael Ellerman [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=43lSbd5fT5z9sMr@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).