From: "Ryan S. Arnold" <ryan.arnold@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, libc-ports@sourceware.org
Subject: Re: Remove pre-2.4.21 Linux kernel support
Date: Wed, 25 Jul 2012 20:50:00 -0000 [thread overview]
Message-ID: <CAAKybw_zTGSbAtWGkXK+1J6SW-dO_c_E2xe0v6e=kpb43DY2Hw@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1207122337590.30566@digraph.polyomino.org.uk>
On Thu, Jul 12, 2012 at 6:39 PM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> Continuing the removal of compatibility code for old Linux kernel
> versions, this patch increases the minimum kernel version from 2.4.1
> to 2.4.21. This allows removal of all conditions on specific 2.4
> kernel versions except for __ASSUME_TMPFS_NAME (where the comment says
> 2.4.20 but the code is actually testing against 2.4.26; I'll deal with
> that when moving the required version to 2.6.0 rather than working out
> whether actually 2.4.21 is enough there).
>
> A fair amount of the patch deals with some macros defined and used
> only for powerpc; could a powerpc maintainer review / test these
> changes? (There are also ports changes to m68k/kernel-features.h, but
> those are trivial.)
>
> There was a single __ASSUME_NETLINK_SUPPORT test outside of
> sysdeps/unix/sysv/linux, but it was only testing whether to define the
> __no_netlink_support variable, previously used by some code that may
> be built into nscd. Since the patch eliminates all uses of that
> variable, the definition in nscd is no longer needed, so in fact all
> __ASSUME_NETLINK_SUPPORT tests can go (there was no substantive use
> relevant to non-Linux kernels) and so this patch removes them all and
> the definition.
>
> Tested x86 and x86_64.
Tested on powerpc32 and powerpc64 and no new regressions were observed.
Ryan S. Arnold
prev parent reply other threads:[~2012-07-25 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 23:40 Joseph S. Myers
2012-07-13 8:24 ` Andreas Schwab
2012-07-13 10:27 ` Joseph S. Myers
2012-07-25 20:50 ` Ryan S. Arnold [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAKybw_zTGSbAtWGkXK+1J6SW-dO_c_E2xe0v6e=kpb43DY2Hw@mail.gmail.com' \
--to=ryan.arnold@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.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).