From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Huacai Chen" <chenhuacai@kernel.org>,
"Aleksandar Markovic" <aleksandar.qemu.devel@gmail.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH 1/2] MIPS: Remove KVM_GUEST support
Date: Wed, 10 Mar 2021 16:07:55 +0100 [thread overview]
Message-ID: <20210310150755.GC12960@alpha.franken.de> (raw)
In-Reply-To: <20210301152958.3480-1-tsbogend@alpha.franken.de>
On Mon, Mar 01, 2021 at 04:29:56PM +0100, Thomas Bogendoerfer wrote:
> KVM_GUEST is broken and unmaintained, so let's remove it.
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> ---
> arch/mips/Kconfig | 17 -
> arch/mips/configs/malta_kvm_guest_defconfig | 436 --------------------
> arch/mips/include/asm/mach-generic/spaces.h | 12 -
> arch/mips/include/asm/processor.h | 5 -
> arch/mips/include/asm/uaccess.h | 9 -
> arch/mips/kernel/cevt-r4k.c | 4 -
> arch/mips/mti-malta/Platform | 6 +-
> arch/mips/mti-malta/malta-time.c | 5 -
> 8 files changed, 1 insertion(+), 493 deletions(-)
> delete mode 100644 arch/mips/configs/malta_kvm_guest_defconfig
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2021-03-10 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 15:29 [PATCH 1/2] MIPS: Remove KVM_GUEST support Thomas Bogendoerfer
2021-03-02 2:27 ` Jiaxun Yang
2021-03-02 4:22 ` Huacai Chen
2021-03-10 15:07 ` Thomas Bogendoerfer [this message]
[not found] ` <20210301152958.3480-2-tsbogend@alpha.franken.de>
2021-03-10 15:08 ` [PATCH 2/2] MIPS: Remove KVM_TE support Thomas Bogendoerfer
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=20210310150755.GC12960@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=f4bug@amsat.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.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).