public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Joseph Myers <jsm28@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] Remove MAP_VARIABLE from hppa bits/mman.h Date: Mon, 5 Jun 2023 14:35:41 +0000 (GMT) [thread overview] Message-ID: <20230605143541.7E1CB38323DC@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=be9b883ddd12acd2baa517fd1b5b8c8be22f733a commit be9b883ddd12acd2baa517fd1b5b8c8be22f733a Author: Joseph Myers <joseph@codesourcery.com> Date: Mon Jun 5 14:35:25 2023 +0000 Remove MAP_VARIABLE from hppa bits/mman.h As suggested in <https://sourceware.org/pipermail/libc-alpha/2023-February/145890.html>, remove the MAP_VARIABLE define from the hppa bits/mman.h, for consistency with Linux 6.2 which removed the define there. Tested with build-many-glibcs.py for hppa-linux-gnu. Diff: --- sysdeps/unix/sysv/linux/hppa/bits/mman.h | 1 - 1 file changed, 1 deletion(-) diff --git a/sysdeps/unix/sysv/linux/hppa/bits/mman.h b/sysdeps/unix/sysv/linux/hppa/bits/mman.h index f5a69693af..651b7dcb72 100644 --- a/sysdeps/unix/sysv/linux/hppa/bits/mman.h +++ b/sysdeps/unix/sysv/linux/hppa/bits/mman.h @@ -24,7 +24,6 @@ /* Other flags. */ #define __MAP_ANONYMOUS 0x10 /* Don't use a file */ -#define MAP_VARIABLE 0 /* These are Linux-specific. */ #define MAP_DENYWRITE 0x0800 /* ETXTBSY */
reply other threads:[~2023-06-05 14:35 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230605143541.7E1CB38323DC@sourceware.org \ --to=jsm28@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).