public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH 2/2] backends: Implement aarch64_dynamic_tag_name and aarch64_dynamic_tag_check
Date: Mon, 07 Sep 2020 09:29:52 +0200	[thread overview]
Message-ID: <2e24f3a7d94a23f16b03b1497d6e5a538601da8d.camel@klomp.org> (raw)
In-Reply-To: <20200828224202.23240-2-mark@klomp.org>

On Sat, 2020-08-29 at 00:42 +0200, Mark Wielaard wrote:
> +2020-08-28  Mark Wielard  <mark@klomp.org>
> +
> +	* aarch64_init.c (aarch64_init): Hook dynamic_tag_name and
> +	dynamic_tag_check.
> +	* aarch64_symbol.c (aarch64_dynamic_tag_name): New function.
> +	(aarch64_dynamic_tag_check): Likewise.

Pushed.

  reply	other threads:[~2020-09-07  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 22:42 [PATCH 1/2] libelf: Sync elf.h from glibc Mark Wielaard
2020-08-28 22:42 ` [PATCH 2/2] backends: Implement aarch64_dynamic_tag_name and aarch64_dynamic_tag_check Mark Wielaard
2020-09-07  7:29   ` Mark Wielaard [this message]
2020-09-07  7:29 ` [PATCH 1/2] libelf: Sync elf.h from glibc 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=2e24f3a7d94a23f16b03b1497d6e5a538601da8d.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@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).