From: Aurelien Jarno <aurelien@aurel32.net>
To: Zack Weinberg <zackw@panix.com>
Cc: Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] alpha: force old OSF1 syscalls for getegid, geteuid and getppid [BZ #24986]
Date: Sat, 14 Sep 2019 18:26:20 +0200 [thread overview]
Message-ID: <20190914162620.GA2961@aurel32.net> (raw)
In-Reply-To: <CAKCAbMiBbV5rB5XdkxVpqGCt+oWd8sZ1xqcgE0jE2g=OyacYrA@mail.gmail.com>
On 2019-09-10 11:44, Zack Weinberg wrote:
> On Tue, Sep 10, 2019 at 10:58 AM Aurelien Jarno <aurelien@aurel32.net> wrote:
> > On 2019-09-10 13:20, Florian Weimer wrote:
> > > * Aurelien Jarno:
> > >
> > > > Changelog:
> > > > [BZ #24986]
> > > > * sysdeps/unix/alpha/getegid.S: Move to ...
> > > > * sysdeps/unix/sysv/linux/alpha/getegid.S: ... here.
> > > > * sysdeps/unix/alpha/geteuid.S: Move to ...
> > > > * sysdeps/unix/sysv/linux/alpha/geteuid.S: ... here.
> > > > * sysdeps/unix/alpha/getppid.S: Move to ...
> > > > * sysdeps/unix/sysv/linux/alpha/getppid.S: ... here
> > >
> > > Looks reasonable to me.
> >
> > The other alternative instead of moving the files is to add those files
> > with a simple #include <sysdeps/unix/alpha/getXXXX.S>. It's the strategy
> > chosen for pipe.S for example.
>
> What are the odds that a hypothetical future port to Alpha with a
> non-Linux kernel would want to use these files, though? If they're
> not likely to be wanted, moving the files is simpler.
There is already little interest for the Linux kernel port, so I really
doubt a non-Linux kernel port will happen. I have therefore committed
the patch.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2019-09-14 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 10:53 [PATCH] alpha: force old OSF1 syscalls for getegid, geteuid and getppid [BZ #24986] Aurelien Jarno
2019-09-10 11:20 ` Florian Weimer
2019-09-10 14:58 ` Aurelien Jarno
2019-09-10 15:44 ` Zack Weinberg
2019-09-14 16:26 ` Aurelien Jarno [this message]
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190914162620.GA2961@aurel32.net \
--to=aurelien@aurel32.net \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=rth@twiddle.net \
--cc=zackw@panix.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).