From: David Daney <ddaney@caviumnetworks.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Include linux/errno.h from arch/mips/include/asm/compat.h
Date: Thu, 16 Apr 2009 09:02:00 -0700 [thread overview]
Message-ID: <49E75678.7050909@caviumnetworks.com> (raw)
In-Reply-To: <20090411.233150.25909696.anemo@mba.ocn.ne.jp>
Atsushi Nemoto wrote:
> On Fri, 10 Apr 2009 12:16:11 -0700, Ralf Baechle <ralf@linux-mips.org> wrote:
>> On Fri, Apr 10, 2009 at 11:41:35AM -0700, David Daney wrote:
>>
>>> The recent change that added #include <linux/seccomp.h> breaks
>>> (because EINVAL is not defined) when building
>>> arch/mips/kernel/asm-offsets.s if CONFIG_SECCOMP is not defined.
>>> Including errno.h fixes the problem.
>> NAK, <linux/seccomp.h> should include <linux/errno.h>.
>
> Then how about this?
>
> ------------------------------------------------------
> Subject: [PATCH] Do not include seccomp.h from compat.h
> From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
>
> The compat.h does not need seccomp.h since TIF_32BIT was moved to
> thread_info.h
>
> This fixes a build error of 64-bit kernel without CONFIG_SECCOMP.
>
> Signed-off-by: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Signed-off-by: David Daney <ddaney@caviumnetworks.com>
> ---
> arch/mips/include/asm/compat.h | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/arch/mips/include/asm/compat.h b/arch/mips/include/asm/compat.h
> index 6c5b409..f58aed3 100644
> --- a/arch/mips/include/asm/compat.h
> +++ b/arch/mips/include/asm/compat.h
> @@ -3,7 +3,6 @@
> /*
> * Architecture specific compatibility types
> */
> -#include <linux/seccomp.h>
> #include <linux/thread_info.h>
> #include <linux/types.h>
> #include <asm/page.h>
>
>
next prev parent reply other threads:[~2009-04-16 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 18:41 [PATCH] MIPS: Include linux/errno.h from arch/mips/include/asm/compat.h David Daney
2009-04-10 19:16 ` Ralf Baechle
2009-04-11 14:31 ` Atsushi Nemoto
2009-04-16 16:02 ` David Daney [this message]
2009-04-18 9:06 ` Ralf Baechle
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=49E75678.7050909@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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