From: Michal Simek <monstr@monstr.eu>
To: Oded Gabbay <oded.gabbay@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] microblaze: add missing include to mmu_context_mm.h
Date: Mon, 30 Oct 2017 14:18:45 +0100 [thread overview]
Message-ID: <b46c02d3-2e58-69ea-d076-04858d06e3cd@monstr.eu> (raw)
In-Reply-To: <20171026084334.30712-1-oded.gabbay@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1331 bytes --]
On 26.10.2017 10:43, Oded Gabbay wrote:
> mmu_context_mm.h is using struct task_struct, which is defined in
> linux/sched.h. Source files that include mm_context_mm.h
> (directly or indirectly) and doesn't include linux/sched.h will generate
> an error. An example of that is drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
>
> This patch adds an include of linux/sched.h to mmu_context_mm.h to avoid
> such errors.
>
> Signed-off-by: Oded Gabbay <oded.gabbay@gmail.com>
> ---
> arch/microblaze/include/asm/mmu_context_mm.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/microblaze/include/asm/mmu_context_mm.h b/arch/microblaze/include/asm/mmu_context_mm.h
> index 99472d2ca340..97559fe0b953 100644
> --- a/arch/microblaze/include/asm/mmu_context_mm.h
> +++ b/arch/microblaze/include/asm/mmu_context_mm.h
> @@ -13,6 +13,7 @@
>
> #include <linux/atomic.h>
> #include <linux/mm_types.h>
> +#include <linux/sched.h>
>
> #include <asm/bitops.h>
> #include <asm/mmu.h>
>
Applied to next.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2017-10-30 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 8:43 Oded Gabbay
2017-10-30 13:18 ` Michal Simek [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=b46c02d3-2e58-69ea-d076-04858d06e3cd@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.com \
/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
all inboxes | Powered by JetHome®