From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: will.deacon@arm.com, Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Michal Simek <monstr@monstr.eu>
Subject: Re: [PATCH] ARM64: fix building without CONFIG_UID16
Date: Mon, 30 Nov 2015 09:38:58 +0100 [thread overview]
Message-ID: <20151130083858.GB4045@osiris> (raw)
In-Reply-To: <3891403.6hGat7eHq5@wuerfel>
On Fri, Nov 20, 2015 at 12:12:21PM +0100, Arnd Bergmann wrote:
> As reported by Michal Simek, building an ARM64 kernel with CONFIG_UID16
> disabled currently fails because the system call table still needs to
> reference the individual function entry points that are provided by
> kernel/sys_ni.c in this case, and the declarations are hidden inside
> of #ifdef CONFIG_UID16:
Will we ever get rid of UID16? kernel/uid.c contains this nice comment:
/*
* Wrapper functions for 16bit uid back compatibility. All nicely tied
* together in the faint hope we can take the out in five years time.
*/
Which seems to exist since at least February 2000. ;)
WARNING: multiple messages have this Message-ID (diff)
From: heiko.carstens@de.ibm.com (Heiko Carstens)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: fix building without CONFIG_UID16
Date: Mon, 30 Nov 2015 09:38:58 +0100 [thread overview]
Message-ID: <20151130083858.GB4045@osiris> (raw)
In-Reply-To: <3891403.6hGat7eHq5@wuerfel>
On Fri, Nov 20, 2015 at 12:12:21PM +0100, Arnd Bergmann wrote:
> As reported by Michal Simek, building an ARM64 kernel with CONFIG_UID16
> disabled currently fails because the system call table still needs to
> reference the individual function entry points that are provided by
> kernel/sys_ni.c in this case, and the declarations are hidden inside
> of #ifdef CONFIG_UID16:
Will we ever get rid of UID16? kernel/uid.c contains this nice comment:
/*
* Wrapper functions for 16bit uid back compatibility. All nicely tied
* together in the faint hope we can take the out in five years time.
*/
Which seems to exist since at least February 2000. ;)
next prev parent reply other threads:[~2015-11-30 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 11:12 [PATCH] ARM64: fix building without CONFIG_UID16 Arnd Bergmann
2015-11-20 11:12 ` Arnd Bergmann
2015-11-20 11:12 ` Arnd Bergmann
2015-11-23 15:22 ` Will Deacon
2015-11-23 15:22 ` Will Deacon
2015-11-25 12:16 ` Catalin Marinas
2015-11-25 12:16 ` Catalin Marinas
2015-11-30 8:38 ` Heiko Carstens [this message]
2015-11-30 8:38 ` Heiko Carstens
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=20151130083858.GB4045@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.