From: Mark Wielaard <mark@klomp.org>
To: Andreas Schwab <schwab@suse.de>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] libelf: Sync elf.h from glibc
Date: Mon, 8 Aug 2022 22:17:35 +0200 [thread overview]
Message-ID: <20220808201735.GB553@gnu.wildebeest.org> (raw)
In-Reply-To: <mvmlerzkliv.fsf@suse.de>
Hi Andreas,
On Mon, Aug 08, 2022 at 01:44:08PM +0200, Andreas Schwab wrote:
> Adds PT_RISCV_ATTRIBUTES, SHT_RISCV_ATTRIBUTES, PT_AARCH64_MEMTAG_MTE,
> RELR definitions, LoongArch relocations.
>
> dwelf_elf_e_machine_string was updated to handle EM_LOONGARCH, and
> ebl_dynamic_tag_name was updated to handle the new RELR dynamic tags.
Thanks, looks good. Pushed.
Cheers,
Mark
next prev parent reply other threads:[~2022-08-08 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 11:44 Andreas Schwab
2022-08-08 20:17 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-13 9:01 Ying Huang
2023-10-13 13:21 ` Mark Wielaard
2023-06-26 14:30 Andreas Schwab
2023-06-27 13:27 ` Mark Wielaard
2018-04-19 15:47 Andreas Schwab
2018-04-23 11:54 ` Mark Wielaard
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=20220808201735.GB553@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=schwab@suse.de \
/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).