public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: David Kilroy <David.Kilroy@arm.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Cc: nd <nd@arm.com>
Subject: RE: [PATCH v3 0/3] elf: Allow dlopen of filter object to work [BZ #16272]
Date: Thu, 19 Dec 2019 11:43:00 -0000	[thread overview]
Message-ID: <DB6PR0801MB17517D22EB2BE89F6B3496AD91520@DB6PR0801MB1751.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <7905f81b-ac11-f097-11f8-3166340d932b@linaro.org>

Adhemerval Zanella wrote:
> On 18/12/2019 13:32, David Kilroy wrote:
> >> Repost of v2 with updated commit message resulting from follow-up
> >> tests with a different implementation.
> >>
> >> I'd still like to see this fixed, but the last patchset didn't get
> any
> >> responses.
> >>
> >> v3:
> >>  - rebased for changes in elf/Makefile
> >>  - updates to commit messages
> >>
> >> v2:
> >> https://sourceware.org/ml/libc-alpha/2019-10/msg00701.html
> >>  - code formatting fixups
> >>  - add dependency of test output on filtee library
> >>  - tests changed to use the test framework
> >>
> >> v1:
> >> https://sourceware.org/ml/libc-alpha/2019-10/msg00519.html
> >
> > Ping.  Is there any interest in taking this series, or something like
> it?
> > I've seen that it needs another (almost trivial) rebase for changes
> in
> > elf/Makefile, but don't want do that unnecessarily.
> 
> I think there is interest, the main problem is always lack of manpower
> and time from reviewers to move this forward. I will try to spend some
> time to review it.

Thanks Adhemerval. I understand - it's not always clear which is the case :)
I'll keep this on my list of things to chase.



Regards,

Dave Kilroy.


      reply	other threads:[~2019-12-19 11:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 17:30 David Kilroy
2019-12-03 17:30 ` [PATCH v3 3/3] elf: avoid stack allocation in dl_open_worker David Kilroy
2020-01-14 20:04   ` Adhemerval Zanella
2019-12-03 17:30 ` [PATCH v3 1/3] elf: Allow dlopen of filter object to work [BZ #16272] David Kilroy
2020-01-14 18:31   ` Adhemerval Zanella
2020-01-15 12:37     ` David Kilroy
2020-01-17 14:04       ` Adhemerval Zanella
2020-01-17 17:00     ` David Kilroy
2020-01-21 16:34       ` David Kilroy
2020-01-22 20:39         ` Adhemerval Zanella
2019-12-03 17:30 ` [PATCH v3 2/3] elf: avoid redundant sort in dlopen David Kilroy
2020-01-14 19:42   ` Adhemerval Zanella
2019-12-18 16:32 ` [PATCH v3 0/3] elf: Allow dlopen of filter object to work [BZ #16272] David Kilroy
2019-12-18 19:33   ` Adhemerval Zanella
2019-12-19 11:43     ` David Kilroy [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=DB6PR0801MB17517D22EB2BE89F6B3496AD91520@DB6PR0801MB1751.eurprd08.prod.outlook.com \
    --to=david.kilroy@arm.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=nd@arm.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).