From: Nick Clifton <nickc@redhat.com>
To: "Martin Storsjö" <martin@martin.st>, binutils@sourceware.org
Subject: Re: [PATCH v2 2/2] ld: pe: Apply review suggestions on the existing exports/imports arrays
Date: Fri, 9 Sep 2022 11:35:51 +0100 [thread overview]
Message-ID: <5320b853-9c31-60a8-aeab-d87ed470ac39@redhat.com> (raw)
In-Reply-To: <20220906154447.1402361-2-martin@martin.st>
Hi Martin,
> Use a separate explicit max_exports/imports field, instead of
> deducing it from the number of allocated elements. Use a named
> constant for the incremental growth of the array.
Patch approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2022-09-09 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 15:44 [PATCH v2 1/2] ld: pe: Improve performance of object file exclude symbol directives Martin Storsjö
2022-09-06 15:44 ` [PATCH v2 2/2] ld: pe: Apply review suggestions on the existing exports/imports arrays Martin Storsjö
2022-09-09 10:35 ` Nick Clifton [this message]
2022-09-09 10:35 ` [PATCH v2 1/2] ld: pe: Improve performance of object file exclude symbol directives Nick Clifton
2022-09-12 8:10 ` Martin Storsjö
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=5320b853-9c31-60a8-aeab-d87ed470ac39@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=martin@martin.st \
/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).