public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: tbaeder@redhat.com
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH 2/2] elf-from-memory: Refactor to get rid of nested function
Date: Thu, 28 Jan 2021 23:58:44 +0100	[thread overview]
Message-ID: <20210128225843.GN8492@wildebeest.org> (raw)
In-Reply-To: <20210108080956.2201985-3-tbaeder@redhat.com>

Hi Timm,

On Fri, Jan 08, 2021 at 09:09:56AM +0100, Timm Bäder via Elfutils-devel wrote:
> Try to unify the 32/64 bit code paths and get rid of the nested
> handle_segment() this way.

The new code does seem to do the same thing as the old code.
Added a ChangeLog entry and pushed.

Thanks,

Mark

      reply	other threads:[~2021-01-28 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08  8:09 Remove nested functions from elf-from-memory.c tbaeder
2021-01-08  8:09 ` [PATCH 1/2] elf-from-memory: Restructure code to get rid of nested handle_segment() tbaeder
2021-01-28 21:08   ` Mark Wielaard
2021-01-08  8:09 ` [PATCH 2/2] elf-from-memory: Refactor to get rid of nested function tbaeder
2021-01-28 22:58   ` Mark Wielaard [this message]

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=20210128225843.GN8492@wildebeest.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=tbaeder@redhat.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.
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).