From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] [PATCH 00/11] updates for linux v5.10
Date: Mon, 15 Feb 2021 09:18:20 -0500 [thread overview]
Message-ID: <20210215141819.GE11590@brightrain.aerifal.cx> (raw)
In-Reply-To: <20210214190224.GB354034@port70.net>
On Sun, Feb 14, 2021 at 08:02:24PM +0100, Szabolcs Nagy wrote:
> * Szabolcs Nagy <nsz@port70.net> [2020-12-23 22:13:23 +0100]:
> > with some missed aarch64 v5.8 bits.
> >
> > i noticed that v5.2 had new syscalls with new macros defined
> > in linux/mount.h, but since those syscalls are undocumented
> > (open_tree, move_mount, fsopen, fsconfig, fsmount and fspick)
> > i think it's fine to leave those macros out but the new flag
> > for mount is added.
> >
> > Szabolcs Nagy (11):
> > bits/syscall.h: add process_madvise from linux v5.10
> > sys/membarrier.h: add new constants from linux v5.10
> > sys/mount.h: add MS_NOSYMFOLLOW from linux v5.10
> > sys/mman.h: add MAP_HUGE_16KB from linux v5.10
> > elf.h: add NT_ARM_TAGGED_ADDR_CTRL from linux v5.10
> > sys/prctl.h: add MTE related constants from linux v5.10
> > signal.h: add MTE specific SIGSEGV codes from linux v5.10
> > aarch64/bits/hwcap.h: add HWCAP2_BTI from linux v5.8
> > add aarch64/bits/mman.h with PROT_BTI from linux v5.8
> > aarch64/bits/hwcap.h: add HWCAP2_MTE from linux v5.10
> > aarch64/bits/mman.h: add PROT_MTE from linux v5.10
>
> ping.
Thanks, applying. BTW could you check that your editor settings for
musl commits wrap at 75 columns or fewer (making 79 with default git
log indent)? I reflowed one of these and another patch a few days ago.
Rich
next prev parent reply other threads:[~2021-02-15 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 21:13 Szabolcs Nagy
2021-02-14 19:02 ` Szabolcs Nagy
2021-02-15 14:18 ` Rich Felker [this message]
2021-02-15 18:36 ` Szabolcs Nagy
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=20210215141819.GE11590@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).