From: Lee Revell <rlrevell@joe-job.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: 7eggert@gmx.de, Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org
Subject: Re: remove CONFIG_UID16
Date: Wed, 21 Dec 2005 18:23:43 -0500 [thread overview]
Message-ID: <1135207424.31433.19.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.61.0512212332450.605@yvahk01.tjqt.qr>
On Wed, 2005-12-21 at 23:33 +0100, Jan Engelhardt wrote:
> >> > It seems noone noticed that CONFIG_UID16 was accidentially always
> >> > disabled in the latest -mm kernels.
> >> >
> >> > Is there any reason against removing it completely?
> >>
> >> Maybe embedded systems.
> >
> >The comments in the code say it's for backwards compatibility:
> >
> >(from include/linux/highuid.h)
> >
> > *
> > * CONFIG_UID16 is defined if the given architecture needs to
> > * support backwards compatibility for old system calls.
> > *
> >
> >This implies that removing it would break some applications, right?
>
>
> So what are the most recent apps that still use them, and for what kernel
> were they originally designed?
I don't think this is a productive line of reasoning, even if we could
not identify one such app. We should not break user visible APIs
without a compelling reason.
Lee
next prev parent reply other threads:[~2005-12-21 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5kCbe-45z-7@gated-at.bofh.it>
2005-12-17 10:28 ` remove CONFIG_UID16 Bodo Eggert
2005-12-17 18:29 ` Lee Revell
2005-12-21 22:33 ` Jan Engelhardt
2005-12-21 23:23 ` Lee Revell [this message]
2005-12-17 4:44 Adrian Bunk
2005-12-17 13:18 ` Christoph Hellwig
2005-12-17 18:38 ` Adrian Bunk
2005-12-22 22:12 ` Bill Davidsen
2005-12-17 19:54 ` Matt Mackall
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=1135207424.31433.19.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=7eggert@gmx.de \
--cc=bunk@stusta.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.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 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.