mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@hockin.org>
To: torvalds@transmeta.com (Linus Torvalds)
Cc: schwidefsky@de.ibm.com (Martin Schwidefsky),
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.41 s390 (8/8): 16 bit uid/gids.
Date: Wed, 9 Oct 2002 10:38:11 -0700 (PDT)	[thread overview]
Message-ID: <200210091738.g99HcBY15929@www.hockin.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210091022050.7355-100000@home.transmeta.com> from "Linus Torvalds" at Oct 09, 2002 10:24:04 AM

> > Use common code for 16 bit user/groud id system calls on s390x.
> 
> Please make this use the real CONFIG_UID16_SYSCALLS instead of using a 
> magic __UID16 thing that is s390x-specific. Then you make everybody who 
> currently uses CONFIG_UID16 do both CONFIG_UID16 and 
> CONFIG_UID16_SYSCALLS.
> 
> We don't want magic config options like __UID16 that aren't exposed as 
> config options and make people go "Huh?!".


Linus, This is actually something I sent to Martin (and DaveM).  The __UID16
crap is because s390x and Sparc64 (and others?) do not want the highuid
stuff except in very specific places - namely compat code.  Just using
CONFIG_UID16_SYSCALLS has the same bad side-effect as CONFIG_UID16 - all or
nothing.  In short, we want to build uid16.o with highuid translations, and
a few other compat objects, but not everything.  Ugly.

I wasn't aware Martin had tried to push this one quite yet.  Have a
preferred solution?  I'd already passed this by DaveM and he said the fun
would be getting it past you :)

Tim

  reply	other threads:[~2002-10-09 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 12:32 Martin Schwidefsky
2002-10-09 17:24 ` Linus Torvalds
2002-10-09 17:38   ` Tim Hockin [this message]
2002-10-09 17:47     ` Linus Torvalds
2002-10-09 18:24       ` Tim Hockin
2002-10-09 22:10         ` Linus Torvalds
2002-10-09 22:43           ` Tim Hockin
2002-10-09 23:12             ` Linus Torvalds
2002-10-09 23:38               ` David S. Miller
2002-10-09 23:59                 ` Tim Hockin

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=200210091738.g99HcBY15929@www.hockin.org \
    --to=thockin@hockin.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=torvalds@transmeta.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®