From: Milian Wolff <mail@milianw.de>
To: Mark Wielaard <mark@klomp.org>
Cc: Aaron Merey <amerey@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: [PATCH] Introduce public dwfl_get_debuginfod_client API
Date: Wed, 13 Jul 2022 23:15:29 +0200 [thread overview]
Message-ID: <1874913.LJ49KAohvX@milian-workstation> (raw)
In-Reply-To: <Ys8tWzRSKeZ+BEI3@wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
On Mittwoch, 13. Juli 2022 22:38:51 CEST Mark Wielaard wrote:
> Hi Milian,
>
> On Wed, Jul 13, 2022 at 09:36:45PM +0200, Milian Wolff wrote:
> > On Mittwoch, 13. Juli 2022 20:20:04 CEST Aaron Merey wrote:
> > > There weren't any concerns with the patch so I've gone ahead and merged
> > > it as commit a4b1839c3c46.
>
> Yeah, sorry, I should have spoken up on the list not just mumbled
> something on irc. My only concern was that I was afraid to pull in
> libdebuginfod.h api by default. But you handled to by making
> debuginfod_client handle an opaque pointer, which it of course is. So
> my worry was unfounded.
>
> But I did just now see it has a typo in libdw.map:
>
> ELFUTILS_0.187 {
> global:
> dwfl_get_debuginfod_client;
> } ELFUTILS_0.186;
>
> That should be ELFUTILS_0.188 we already released 0.187.
Ah, thanks for spotting that.
> Also (micro optimazition to prevent a PLT call) the internal calls
> should use INTUSE (dwfl_get_debuginfod_client).
TIL, thanks. I probably will never feel at home in C code bases with all these
arcane macros :D
> I made both changes and added a NEWS entry. See attached.
LGTM.
> > I got spammed by a flood of mails from buildbot, but from what I can tell
> > the issues are all unrelated to my patch? Or did I break something? See
> > e.g.:
> >
> > [1]: https://builder.sourceware.org/buildbot/#/builders/39/builds/41
>
> Those are unrelated to your patch
OK, thanks.
--
Milian Wolff
mail@milianw.de
http://milianw.de
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-07-13 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 14:46 Milian Wolff
2022-07-07 16:40 ` Aaron Merey
2022-07-07 16:58 ` Milian Wolff
2022-07-07 17:09 ` Aaron Merey
2022-07-07 17:33 ` Milian Wolff
2022-07-07 17:42 ` Aaron Merey
2022-07-13 18:20 ` Aaron Merey
2022-07-13 19:36 ` Milian Wolff
2022-07-13 20:35 ` Aaron Merey
2022-07-13 20:38 ` Mark Wielaard
2022-07-13 21:15 ` Milian Wolff [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=1874913.LJ49KAohvX@milian-workstation \
--to=mail@milianw.de \
--cc=amerey@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).