From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: George Burgess IV <george.burgess.iv@gmail.com>,
libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH] Refactoring FORTIFY
Date: Tue, 03 Oct 2017 19:34:00 -0000 [thread overview]
Message-ID: <9ea2b3d3-c7d0-1d36-db4d-4de7b21067f1@linaro.org> (raw)
In-Reply-To: <CAKh6zBFAGomCFc+Y9=qpH-2N6AonKUja1R+cWy=p_=T=rs29cQ@mail.gmail.com>
On 11/09/2017 03:26, George Burgess IV wrote:
> Hello,
>
> Attached is a patch that aims to substantially improve FORTIFY's
> usefulness with clang, and make defining FORTIFY'ed functions require
> less ceremony.
Due the patch size and complexity and no indication on the message, it
would be good to know if you already have a copyright assignment, and
if your work is covered by it.
You will need it to sort this out first so someone can actually look
into your patch (which I am interested in review btw).
next prev parent reply other threads:[~2017-10-03 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 6:27 George Burgess IV
2017-10-02 20:12 ` George Burgess IV
2017-10-03 19:34 ` Adhemerval Zanella [this message]
2017-10-03 20:54 ` George Burgess IV
2017-10-05 13:43 ` Adhemerval Zanella
2017-10-05 15:48 ` Joseph Myers
2017-10-05 20:06 ` Adhemerval Zanella
2017-11-06 19:12 ` George Burgess IV
2017-11-20 20:03 ` Adhemerval Zanella
2017-12-05 4:53 ` George Burgess IV
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=9ea2b3d3-c7d0-1d36-db4d-4de7b21067f1@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=george.burgess.iv@gmail.com \
--cc=libc-alpha@sourceware.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).