From: "H.J. Lu" <hjl.tools@gmail.com>
To: Kaylee Blake <klkblake@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 0/7] ELF: Don't require section header on ELF objects
Date: Sat, 2 May 2020 07:19:10 -0700 [thread overview]
Message-ID: <CAMe9rOp5A2PJ9BK2eeZzUy3FQuMxFHYQc+SeyePbibRfmutwtQ@mail.gmail.com> (raw)
In-Reply-To: <552bbcda-9d3e-d895-16d0-4f6b7d96d9a1@gmail.com>
On Wed, Mar 18, 2020 at 6:46 PM Kaylee Blake via Binutils
<binutils@sourceware.org> wrote:
>
> On 19/3/20 12:02 pm, H.J. Lu wrote:
> > Kaylee, is your paper work with FSF in order? I will submit the updated
> > patch set after your paper is on file with FSF.
>
> I'm waiting on a response from them at the moment.
>
Hi Kaylee,
Any update on your paper work with FSF?
--
H.J.
next prev parent reply other threads:[~2020-05-02 14:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 23:42 H.J. Lu
2020-03-08 23:42 ` [PATCH 1/7] " H.J. Lu
2020-03-08 23:42 ` [PATCH 2/7] bfd: Reconstruct dynamic symbol table from PT_DYNAMIC segment H.J. Lu
2020-03-08 23:42 ` [PATCH 3/7] readelf: Compute dynamic symbol table size from hash table H.J. Lu
2020-03-08 23:42 ` [PATCH 4/7] ld: Add a simple test for -z nosectionheader H.J. Lu
2020-03-08 23:42 ` [PATCH 5/7] binutils: Add --remove-section-header tests H.J. Lu
2020-03-08 23:42 ` [PATCH 6/7] ld: Add tests for -z nosectionheader and --remove-section-header H.J. Lu
2020-03-08 23:42 ` [PATCH 7/7] ld: Add -z nosectionheader test to bootstrap.exp H.J. Lu
2020-03-19 0:48 ` [PATCH 0/7] ELF: Don't require section header on ELF objects Fangrui Song
2020-03-19 1:32 ` H.J. Lu
2020-03-19 1:45 ` Kaylee Blake
2020-05-02 14:19 ` H.J. Lu [this message]
[not found] ` <06c41571-09ef-d107-ee21-38af17f6d20b@gmail.com>
2020-08-07 13:11 ` Has FSF stopped processing copyright paperwork? H.J. Lu
2020-08-07 13:28 ` Richard Biener
2020-08-14 15:25 ` Kaylee Blake
2021-04-02 13:45 ` H.J. Lu
2021-04-02 15:21 ` 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=CAMe9rOp5A2PJ9BK2eeZzUy3FQuMxFHYQc+SeyePbibRfmutwtQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=klkblake@gmail.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).