From: Michael Ellerman <mpe@ellerman.id.au>
To: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
keescook@chromium.org, re.emese@gmail.com,
kernel-hardening@lists.openwall.com, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [kernel-hardening] Re: [PATCH] gcc-plugins: update architecture list in documentation
Date: Mon, 20 Mar 2017 19:39:48 +1100 [thread overview]
Message-ID: <87var44a0b.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170320065522.14839-1-andrew.donnellan@au1.ibm.com>
Andrew Donnellan <andrew.donnellan@au1.ibm.com> writes:
> Commit 65c059bcaa73 ("powerpc: Enable support for GCC plugins") enabled GCC
> plugins on powerpc, but neglected to update the architecture list in the
> docs. Rectify this.
>
> Fixes: 65c059bcaa73 ("powerpc: Enable support for GCC plugins")
> Signed-off-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
> ---
> Documentation/gcc-plugins.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
It would be nice to merge this for v4.11, so the docs are up to do date
with the code for the release.
I'm not sure who owns it though, should it go via Jon as docs
maintainer (added to CC), or via Kees tree or mine?
cheers
>
> diff --git a/Documentation/gcc-plugins.txt b/Documentation/gcc-plugins.txt
> index 891c69464434..433eaefb4aa1 100644
> --- a/Documentation/gcc-plugins.txt
> +++ b/Documentation/gcc-plugins.txt
> @@ -18,8 +18,8 @@ because gcc versions 4.5 and 4.6 are compiled by a C compiler,
> gcc-4.7 can be compiled by a C or a C++ compiler,
> and versions 4.8+ can only be compiled by a C++ compiler.
>
> -Currently the GCC plugin infrastructure supports only the x86, arm and arm64
> -architectures.
> +Currently the GCC plugin infrastructure supports only the x86, arm, arm64 and
> +powerpc architectures.
>
> This infrastructure was ported from grsecurity [6] and PaX [7].
>
> --
> Andrew Donnellan OzLabs, ADL Canberra
> andrew.donnellan@au1.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2017-03-20 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 6:55 [kernel-hardening] [PATCH] gcc-plugins: update architecture list in documentation Andrew Donnellan
2017-03-20 8:39 ` Michael Ellerman [this message]
2017-03-20 17:01 ` [kernel-hardening] " Kees Cook
2017-03-21 7:00 ` Michael Ellerman
2017-03-22 12:02 ` [kernel-hardening] " Michael Ellerman
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=87var44a0b.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=andrew.donnellan@au1.ibm.com \
--cc=corbet@lwn.net \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=re.emese@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