[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160302215711.7ba0301691f3eb3f5316b861@gmail.com>
Date: Wed, 2 Mar 2016 21:57:11 +0100
From: Emese Revfy <re.emese@...il.com>
To: Kees Cook <keescook@...omium.org>
Cc: linux-kbuild <linux-kbuild@...r.kernel.org>, PaX Team
<pageexec@...email.hu>, Brad Spengler <spender@...ecurity.net>,
"kernel-hardening@...ts.openwall.com"
<kernel-hardening@...ts.openwall.com>, Michal Marek <mmarek@...e.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>, Fengguang Wu
<fengguang.wu@...el.com>
Subject: Re: [PATCH v4 1/3] GCC plugin infrastructure
On Tue, 1 Mar 2016 11:07:25 -0800
Kees Cook <keescook@...omium.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@...omium.org>
> > +R: Emese Revfy <re.emese@...il.com>
> > +L: kernel-hardening@...ts.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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
