From: Mark Wielaard <mark@klomp.org>
To: tbaeder@redhat.com, elfutils-devel@sourceware.org
Subject: Re: [PATCH 3/3] link_map: Inline consider_phdr() into only caller
Date: Sun, 06 Dec 2020 14:39:20 +0100 [thread overview]
Message-ID: <16625fcb9661a69df025689b2c22dd22a9e6e1b0.camel@klomp.org> (raw)
In-Reply-To: <20201201083854.1870943-4-tbaeder@redhat.com>
Hi Timm,
On Tue, 2020-12-01 at 09:38 +0100, Timm Bäder via Elfutils-devel wrote:
> This gets rid of the tested function and is shorter.
It is slightly shorter indeed. Although I changed a couple of lines to
not exceed 80 chars. And I added a ChangeLog entry to
libdwfl/ChangeLog.
Pushed.
Mark
next prev parent reply other threads:[~2020-12-06 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 8:38 link_map: Remove nested functions tbaeder
2020-12-01 8:38 ` [PATCH 1/3] link_map: Pull release_buffer() into file scope tbaeder
2020-12-06 13:20 ` Mark Wielaard
2020-12-01 8:38 ` [PATCH 2/3] link_map: Pull read_addrs() in " tbaeder
2020-12-01 8:38 ` [PATCH 3/3] link_map: Inline consider_phdr() into only caller tbaeder
2020-12-06 13:39 ` Mark Wielaard [this message]
2020-12-06 13:41 ` link_map: Remove nested functions 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=16625fcb9661a69df025689b2c22dd22a9e6e1b0.camel@klomp.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).