From: Christoph Hellwig <hch@lst•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Richard Weinberger <richard@nod•at>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Christoph Hellwig <hch@lst•de>, Al Viro <viro@zeniv•linux.org.uk>
Subject: Re: linux-next: build failure after merge of the uml tree
Date: Wed, 22 Dec 2021 09:16:40 +0100 [thread overview]
Message-ID: <20211222081640.GA22041@lst.de> (raw)
In-Reply-To: <20211222105521.31b14a32@canb.auug.org.au>
On Wed, Dec 22, 2021 at 10:55:21AM +1100, Stephen Rothwell wrote:
> I am not sure what caused this - presumably some include file tidying up.
Yes, it needs this as a fixup:
diff --git a/arch/x86/kvm/mmu/spte.c b/arch/x86/kvm/mmu/spte.c
index 0c76c45fdb686..fad546df0bbac 100644
--- a/arch/x86/kvm/mmu/spte.c
+++ b/arch/x86/kvm/mmu/spte.c
@@ -16,6 +16,7 @@
#include "spte.h"
#include <asm/e820/api.h>
+#include <asm/memtype.h>
#include <asm/vmx.h>
static bool __read_mostly enable_mmio_caching = true;
prev parent reply other threads:[~2021-12-22 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 23:55 linux-next: build failure after merge of the uml tree Stephen Rothwell
2021-12-22 8:16 ` Christoph Hellwig [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=20211222081640.GA22041@lst.de \
--to=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=richard@nod$(echo .)at \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=viro@zeniv$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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