public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Helge Deller <deller@gmx.de>
Cc: <libc-alpha@sourceware.org>, <dave.anglin@bell.net>,
	<fweimer@redhat.com>
Subject: Re: [PATCH v2] hppa: Drop old parisc-specific MADV_* constants
Date: Wed, 22 Feb 2023 15:35:09 +0000	[thread overview]
Message-ID: <218a1225-a5d3-cb3-7f2e-9f4785e14dd@codesourcery.com> (raw)
In-Reply-To: <Y+ZGdUZ+XsYloL1a@ls3530>

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.  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?

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2023-02-22 15:35 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 [this message]
2023-02-25 20:09   ` Helge Deller

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=218a1225-a5d3-cb3-7f2e-9f4785e14dd@codesourcery.com \
    --to=joseph@codesourcery.com \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=fweimer@redhat.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).