From: Emese Revfy <re.emese@gmail.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: kernel-hardening@lists.openwall.com, pageexec@freemail.hu,
spender@grsecurity.net, mmarek@suse.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, yamada.masahiro@socionext.com,
linux-kbuild@vger.kernel.org, minipli@ld-linux.so,
linux@armlinux.org.uk, catalin.marinas@arm.com,
linux@rasmusvillemoes.dk, david.brown@linaro.org,
benh@kernel.crashing.org, tglx@linutronix.de,
akpm@linux-foundation.org, jlayton@poochiereds.net,
arnd@arndb.de
Subject: Re: [kernel-hardening] [PATCH v1 0/2] Introduce the initify gcc plugin
Date: Tue, 28 Jun 2016 18:14:56 +0200 [thread overview]
Message-ID: <20160628181456.21c1f567271b6f19fac1d886@gmail.com> (raw)
In-Reply-To: <20160628125748.GK31744@leverpostej>
On Tue, 28 Jun 2016 13:57:49 +0100
Mark Rutland <mark.rutland@arm.com> wrote:
> On Tue, Jun 28, 2016 at 01:34:07PM +0200, Emese Revfy wrote:
> > This patch set is based on the "Add support for complex gcc plugins that
> > don't fit in a single file" patch set (git/kees/linux.git#kspp HEAD:
> > e5d4798b284cd192c8b).
>
> I was hoping to give this a spin on arm/arm64, but I couldn't find the
> prerequisite branch/tag/commit in that tree:
>
> https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git/commit/?id=e5d4798b284cd192c8b
>
> Where should I be looking?
Sorry, this commit was disappear. You can apply these patches to this tree:
https://github.com/ephox-gcc-plugins/gcc-plugins_linux-next.git (initify branch)
--
Emese
next prev parent reply other threads:[~2016-06-28 16:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 11:34 [PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy
2016-06-28 11:35 ` [PATCH v1 1/2] Add " Emese Revfy
2016-06-28 21:05 ` Rasmus Villemoes
2016-06-29 14:50 ` Kees Cook
2016-06-29 19:03 ` Emese Revfy
2016-06-28 11:36 ` [PATCH v1 2/2] Mark functions with the __nocapture attribute Emese Revfy
2016-06-28 16:43 ` Joe Perches
2016-06-28 20:40 ` Emese Revfy
2016-06-28 21:00 ` Joe Perches
2016-06-29 18:42 ` Emese Revfy
2016-06-30 0:12 ` Joe Perches
2016-07-01 14:03 ` Emese Revfy
2016-06-28 20:50 ` Rasmus Villemoes
2016-06-28 21:38 ` PaX Team
2016-06-28 22:41 ` Rasmus Villemoes
2016-06-29 18:39 ` Emese Revfy
2016-06-28 11:42 ` [PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy
2016-06-28 12:57 ` [kernel-hardening] " Mark Rutland
2016-06-28 16:14 ` Emese Revfy [this message]
2016-06-28 20:46 ` Kees Cook
2016-06-29 8:21 ` Mark Rutland
2016-06-29 17:52 ` Mark Rutland
2016-06-29 18:28 ` Emese Revfy
2016-06-28 16:35 ` Joe Perches
2016-06-28 18:48 ` Joe Perches
2016-06-28 19:02 ` Rasmus Villemoes
2016-06-28 20:29 ` Emese Revfy
2016-06-28 17:00 ` Mathias Krause
2016-06-28 20:29 ` Emese Revfy
2016-06-28 21:49 ` Joe Perches
2016-06-28 22:07 ` [kernel-hardening] " Valdis.Kletnieks
2016-06-28 23:54 ` Joe Perches
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=20160628181456.21c1f567271b6f19fac1d886@gmail.com \
--to=re.emese@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=david.brown@linaro.org \
--cc=jlayton@poochiereds.net \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=mark.rutland@arm.com \
--cc=minipli@ld-linux.so \
--cc=mmarek@suse.com \
--cc=pageexec@freemail.hu \
--cc=spender@grsecurity.net \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.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