From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Mike Frysinger <vapier@gentoo.org>,
Roland McGrath <roland@hack.frob.com>,
<libc-ports@sourceware.org>
Subject: Re: [PATCH] hppa: add missing prlimit64 symbol
Date: Sun, 12 Aug 2012 16:03:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1208121558220.4075@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CADZpyixTwCs2Buhqo7oEW9A9XEHSE1SuAS-Pz7RK9O-_ggYdbg@mail.gmail.com>
On Sun, 12 Aug 2012, Carlos O'Donell wrote:
> I've been spending the weekend bringing up new hardware for my hppa
> testing, so hopefully I can get back to tackling the maintenance
> backlog (along with any 2.15 and 2.16 backport requests).
A large proportion of the issues I listed, and of the subsequent global
changes needing hppa versions, and quite possibly of the open hppa ports
issues in Bugzilla, could be done purely as mechanical changes without
hardware testing, to reduce the size of the backlog. It's finding and
fixing the issues missing from my list that will need proper testing.
(For reference, my notes of ports changes (for more than just hppa - there
are alpha and ia64 issues here too) that would be appropriate given
post-2.16 libc changes but haven't yet been done:
[2012-08-07] hppa cleanup __ASSUME_LWS_CAS
[2012-08-02] am33, ia64 ASM_TYPE_DIRECTIVE
[2012-07-17] alpha, hppa, ia64 TLS configure checks remove
[2012-07-17] hppa, am33 (and SH) c++-types data
[2012-07-10] am33 ASM_GLOBAL_DIRECTIVE
)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-08-12 16:03 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 [this message]
2012-08-12 14:48 ` Mike Frysinger
2012-08-12 14:51 ` Carlos O'Donell
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=Pine.LNX.4.64.1208121558220.4075@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@systemhalted.org \
--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).