From: Helge Deller <deller@gmx.de>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, dave.anglin@bell.net, fweimer@redhat.com
Subject: Re: [PATCH v2] hppa: Drop old parisc-specific MADV_* constants
Date: Sat, 25 Feb 2023 21:09:02 +0100 [thread overview]
Message-ID: <b0f4d702-0581-b3a1-ac40-c2065fede970@gmx.de> (raw)
In-Reply-To: <218a1225-a5d3-cb3-7f2e-9f4785e14dd@codesourcery.com>
Hi Joseph,
On 2/22/23 16:35, Joseph Myers wrote:
> On Fri, 10 Feb 2023, Helge Deller via Libc-alpha wrote:
>
>> The Linux kernel upstream commit 71bdea6f798b ("parisc: Align parisc
>> MADV_XXX constants with all other architectures") dropped the
>> parisc-specific MADV_* values in favour of the same constants as
>> other architectures. In the same commit a wrapper was added which
>
> I'd like to enquire about another part of that commit. It removes the
> #define of MAP_VARIABLE to 0, so resulting in tst-mman-consts failing if I
> update build-many-glibcs.py to use Linux 6.2.
Oh, didn't knew that.
Basically it wasn't necessary to drop MAP_VARIABLE, but since no other arch
defined it either and as it's not used anywhere in the kernel I assumed it's
ok to drop it.
> So we'll need to change
> tst-mman-consts.py to allow variation between userspace and kernel
> regarding whether that macro is defined (the expectation of the test being
> that newer kernels only add macros tested for, not remove them), but
> should we also remove that define in glibc?
Yes, I think that's the best solution. Keeps glibc and kernel in sync.
Thank you!
Helge
prev parent reply other threads:[~2023-02-25 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 13:28 Helge Deller
2023-02-10 21:48 ` Joseph Myers
2023-02-11 6:37 ` Helge Deller
2023-02-11 15:56 ` John David Anglin
2023-02-22 15:35 ` Joseph Myers
2023-02-25 20:09 ` Helge Deller [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=b0f4d702-0581-b3a1-ac40-c2065fede970@gmx.de \
--to=deller@gmx.de \
--cc=dave.anglin@bell.net \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).