From: Nick Clifton <nickc@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Binutils <binutils@sourceware.org>
Cc: Noah Goldstein <goldstein.w.n@gmail.com>,
Sam James <sam@gentoo.org>, Alan Modra <amodra@gmail.com>
Subject: Re: PING: [PATCH v12 0/6] elf: Use mmap to map in section contents
Date: Wed, 3 Apr 2024 17:03:22 +0100 [thread overview]
Message-ID: <3155c25f-be08-45be-81a5-36777070a5ae@redhat.com> (raw)
In-Reply-To: <CAMe9rOpOM9qctVFVm=Jv4HFZfeM2VZ7y5nNWm=r+toDdYqAU3g@mail.gmail.com>
Hi H.J.
>> Changes in v12:
>>
>> 1. Don't call _bfd_elf_link_keep_memory for x86 since it always returns
>> false.
>> 2. Make _bfd_elf_link_keep_memory static.
> PING.
Sorry for the delay.
Patch series approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2024-04-03 16:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 12:19 H.J. Lu
2024-03-17 12:19 ` [PATCH v12 1/6] elf: Use mmap to map in read-only sections H.J. Lu
2024-04-08 3:57 ` Simon Marchi
2024-04-08 14:26 ` [PATCH] bfd: Define pagesize variables only for mmap H.J. Lu
2024-04-08 22:55 ` Alan Modra
2024-04-09 2:49 ` H.J. Lu
2024-04-09 5:47 ` Alan Modra
2024-04-09 14:25 ` H.J. Lu
2024-03-17 12:19 ` [PATCH v12 2/6] elf: Add _bfd_elf_m[un]map_section_contents H.J. Lu
2024-03-17 12:19 ` [PATCH v12 3/6] elf: Use mmap to map in symbol and relocation tables H.J. Lu
2024-03-17 12:19 ` [PATCH v12 4/6] elf: Don't cache symbol nor relocation tables with mmap H.J. Lu
2024-03-17 12:19 ` [PATCH v12 5/6] elf: Always keep symbol table and relocation info for eh_frame H.J. Lu
2024-03-17 12:19 ` [PATCH v12 6/6] elf: Add _bfd_elf_link_m[un]map_section_contents H.J. Lu
2024-03-28 13:29 ` PING: [PATCH v12 0/6] elf: Use mmap to map in section contents H.J. Lu
2024-04-03 16:03 ` Nick Clifton [this message]
2024-04-04 13:12 ` Luis Machado
2024-04-04 13:53 ` H.J. Lu
2024-04-04 20:27 ` Joseph Myers
2024-04-04 22:22 ` Alan Modra
2024-04-04 22:43 ` Joseph Myers
2024-04-04 22:46 ` H.J. Lu
2024-04-04 23:20 ` H.J. Lu
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=3155c25f-be08-45be-81a5-36777070a5ae@redhat.com \
--to=nickc@redhat.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=goldstein.w.n@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=sam@gentoo.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).