From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Cc: Dave Hansen <dave.hansen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
"open list:ABI/API"
<linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-arch <linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Build failures in -next: sys_pkey_mprotect etc. undefined
Date: Mon, 12 Sep 2016 16:59:30 +0200 [thread overview]
Message-ID: <9369809.1DWhqOZ7mo@wuerfel> (raw)
In-Reply-To: <9d74497b-1522-b350-42fa-49df2df48c4a-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
On Monday, September 12, 2016 7:55:33 AM CEST Guenter Roeck wrote:
> Building h8300:allnoconfig ... failed
> Building h8300:h8300h-sim_defconfig ... failed
> Building c6x:dsk6455_defconfig ... failed
>
> [ and more builds for the same architectures ]
>
> --------------
> Error log:
> arch/h8300/kernel/built-in.o:(.data+0x480): undefined reference to `sys_pkey_mprotect'
> arch/h8300/kernel/built-in.o:(.data+0x484): undefined reference to `sys_pkey_alloc'
> arch/h8300/kernel/built-in.o:(.data+0x488): undefined reference to `sys_pkey_free'
>
> Other architectures (frv, xtensa, score) currently fail to build for other reasons,
> so I don't really know if the above are the only ones affected.
>
>
I think the best solution would be to add them to kernel/sys_ni.c so we can
assign syscall numbers for all architectures regardless of whether they use it
or not (most of them will never use these AFAICT).
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Build failures in -next: sys_pkey_mprotect etc. undefined
Date: Mon, 12 Sep 2016 16:59:30 +0200 [thread overview]
Message-ID: <9369809.1DWhqOZ7mo@wuerfel> (raw)
Message-ID: <20160912145930.gz04m_kds7Xp3_L0oUPzRoJzEijSwIuZ6aAnjGQqFAU@z> (raw)
In-Reply-To: <9d74497b-1522-b350-42fa-49df2df48c4a@roeck-us.net>
On Monday, September 12, 2016 7:55:33 AM CEST Guenter Roeck wrote:
> Building h8300:allnoconfig ... failed
> Building h8300:h8300h-sim_defconfig ... failed
> Building c6x:dsk6455_defconfig ... failed
>
> [ and more builds for the same architectures ]
>
> --------------
> Error log:
> arch/h8300/kernel/built-in.o:(.data+0x480): undefined reference to `sys_pkey_mprotect'
> arch/h8300/kernel/built-in.o:(.data+0x484): undefined reference to `sys_pkey_alloc'
> arch/h8300/kernel/built-in.o:(.data+0x488): undefined reference to `sys_pkey_free'
>
> Other architectures (frv, xtensa, score) currently fail to build for other reasons,
> so I don't really know if the above are the only ones affected.
>
>
I think the best solution would be to add them to kernel/sys_ni.c so we can
assign syscall numbers for all architectures regardless of whether they use it
or not (most of them will never use these AFAICT).
Arnd
next prev parent reply other threads:[~2016-09-12 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 14:55 Build failures in -next: sys_pkey_mprotect etc. undefined Guenter Roeck
[not found] ` <9d74497b-1522-b350-42fa-49df2df48c4a-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-09-12 14:59 ` Arnd Bergmann [this message]
2016-09-12 14:59 ` Arnd Bergmann
2016-09-12 15:03 ` Dave Hansen
2016-09-12 15:03 ` Dave Hansen
2016-09-12 20:09 ` Dave Hansen
[not found] ` <57D70B6D.6010208-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-09-12 20:28 ` Arnd Bergmann
2016-09-12 20:28 ` Arnd Bergmann
2016-09-12 20:33 ` Guenter Roeck
2016-09-12 20:34 ` Dave Hansen
2016-09-12 20:34 ` Dave Hansen
2016-09-12 20:32 ` Guenter Roeck
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=9369809.1DWhqOZ7mo@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=dave.hansen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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).