From: "Carlos O'Donell" <carlos@systemhalted.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Roland McGrath <roland@hack.frob.com>,
libc-ports@sourceware.org
Subject: Re: [PATCH] hppa: add missing prlimit64 symbol
Date: Sun, 12 Aug 2012 14:51:00 -0000 [thread overview]
Message-ID: <CADZpyizQz_i8c+1Z-yFp_o3TJ=Yo5pwpLsNNyAC6d1uPGvY+LA@mail.gmail.com> (raw)
In-Reply-To: <201208121048.31823.vapier@gentoo.org>
On Sun, Aug 12, 2012 at 10:48 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Sunday 12 August 2012 08:59:20 Joseph S. Myers wrote:
>> (Adding the entry, but with @@GLIBC_2.17 like the SH fanotify_mark, to the
>> hppa syscalls.list along with an appropriate Versions entry, is certainly
>> the safer approach than doing something with the potential to affect other
>> architectures, even though it may also be good to work out how to clean
>> these things up. Note hppa also needs fanotify_mark at a new version, and
>> note that cleanups here only help existing architectures;
>
> i originally posted just an entry updating hppa but was encouraged at looking
> at cleaning up everyone
>
>> there are no
>> issues for new architectures using linux-generic because linux-generic
>> already has the right entries in syscalls.list.)
>
> if all new arches are expected to start with linux-generic as its base, then i
> can see leaning towards just adding the entry to hppa and being done with it
Agreed. That's a practical and immediate fix.
Cheers,
Carlos.
next prev parent reply other threads:[~2012-08-12 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 23:00 Mike Frysinger
2012-04-12 23:07 ` Roland McGrath
2012-04-12 23:26 ` Mike Frysinger
2012-04-13 3:59 ` Roland McGrath
2012-08-11 19:27 ` Mike Frysinger
2012-08-12 12:59 ` Joseph S. Myers
2012-08-12 13:15 ` Carlos O'Donell
2012-08-12 16:03 ` Joseph S. Myers
2012-08-12 14:48 ` Mike Frysinger
2012-08-12 14:51 ` Carlos O'Donell [this message]
2012-08-12 15:58 ` Joseph S. Myers
2012-08-12 15:00 ` Mike Frysinger
2012-04-13 2:00 ` Carlos O'Donell
2012-04-13 2:02 ` Carlos O'Donell
2012-04-13 2:21 ` Mike Frysinger
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='CADZpyizQz_i8c+1Z-yFp_o3TJ=Yo5pwpLsNNyAC6d1uPGvY+LA@mail.gmail.com' \
--to=carlos@systemhalted.org \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.com \
--cc=vapier@gentoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).