From: Emese Revfy <re.emese@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
PaX Team <pageexec@freemail.hu>,
Brad Spengler <spender@grsecurity.net>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Michal Marek <mmarek@suse.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH v4 1/3] GCC plugin infrastructure
Date: Wed, 2 Mar 2016 21:57:11 +0100 [thread overview]
Message-ID: <20160302215711.7ba0301691f3eb3f5316b861@gmail.com> (raw)
In-Reply-To: <CAGXu5j+gTWR_ZMk6nMzMZRfTvvi7VXg5ngoHx6cC+r-fe1OgNA@mail.gmail.com>
On Tue, 1 Mar 2016 11:07:25 -0800
Kees Cook <keescook@chromium.org> wrote:
> I wonder if it might make sense to split the .so-building logic
> changes from the gcc plugin changes to make things more readable for
> review? Personally, I'm fine with this as-is, but it might benefit
> other reviewers, if it's a sane split.
I will split this patch in the next patch set.
> > +GCC PLUGINS
> > +M: Kees Cook <keescook@chromium.org>
> > +R: Emese Revfy <re.emese@gmail.com>
> > +L: kernel-hardening@lists.openwall.com
> > +S: Maintained
> > +F: tools/gcc
>
> I think that needs a trailing slash to indicate it's a tree to match.
I tested it with get_maintainer.pl and it is good.
> > +F: Documentation/gcc-plugins.txt
>
> I wonder if this should be moved to Documentation/kbuild/ ?
I don't know. Michal Marek, could you please tell me where I should put the documentation?
--
Emese
next prev parent reply other threads:[~2016-03-02 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 17:14 [PATCH v4 0/3] Introduce GCC plugin infrastructure Emese Revfy
2016-03-01 17:15 ` [PATCH v4 1/3] " Emese Revfy
2016-03-01 19:07 ` Kees Cook
2016-03-02 20:57 ` Emese Revfy [this message]
2016-03-01 21:19 ` Kees Cook
2016-03-01 21:34 ` Kees Cook
2016-03-02 21:18 ` Emese Revfy
2016-03-01 22:50 ` Kees Cook
2016-03-02 21:33 ` PaX Team
2016-03-01 17:16 ` [PATCH v4 2/3] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-03-01 17:17 ` [PATCH v4 3/3] Documentation for the GCC plugin infrastructure Emese Revfy
2016-03-01 19:09 ` [PATCH v4 0/3] Introduce " Kees Cook
2016-03-01 19:16 ` Kees Cook
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=20160302215711.7ba0301691f3eb3f5316b861@gmail.com \
--to=re.emese@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mmarek@suse.com \
--cc=pageexec@freemail.hu \
--cc=spender@grsecurity.net \
/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