From: Kees Cook <keescook@chromium.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Emese Revfy <re.emese@gmail.com>,
Michal Marek <michal.lkml@markovi.net>,
kernel-hardening@lists.openwall.com, linux-doc@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc-plugins: fix gcc-plugins directory path in documentation
Date: Tue, 25 Feb 2020 10:58:28 -0800 [thread overview]
Message-ID: <202002251057.C4E397A@keescook> (raw)
In-Reply-To: <20200213122410.1605-1-masahiroy@kernel.org>
On Thu, Feb 13, 2020 at 09:24:10PM +0900, Masahiro Yamada wrote:
> Fix typos "plgins" -> "plugins".
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Thanks!
Acked-by: Kees Cook <keescook@chromium.org>
Jon, can you take this?
-Kees
> ---
>
> Documentation/kbuild/reproducible-builds.rst | 2 +-
> scripts/gcc-plugins/Kconfig | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/kbuild/reproducible-builds.rst b/Documentation/kbuild/reproducible-builds.rst
> index 503393854e2e..3b25655e441b 100644
> --- a/Documentation/kbuild/reproducible-builds.rst
> +++ b/Documentation/kbuild/reproducible-builds.rst
> @@ -101,7 +101,7 @@ Structure randomisation
>
> If you enable ``CONFIG_GCC_PLUGIN_RANDSTRUCT``, you will need to
> pre-generate the random seed in
> -``scripts/gcc-plgins/randomize_layout_seed.h`` so the same value
> +``scripts/gcc-plugins/randomize_layout_seed.h`` so the same value
> is used in rebuilds.
>
> Debug info conflicts
> diff --git a/scripts/gcc-plugins/Kconfig b/scripts/gcc-plugins/Kconfig
> index e3569543bdac..7b63c819610c 100644
> --- a/scripts/gcc-plugins/Kconfig
> +++ b/scripts/gcc-plugins/Kconfig
> @@ -86,7 +86,7 @@ config GCC_PLUGIN_RANDSTRUCT
> source tree isn't cleaned after kernel installation).
>
> The seed used for compilation is located at
> - scripts/gcc-plgins/randomize_layout_seed.h. It remains after
> + scripts/gcc-plugins/randomize_layout_seed.h. It remains after
> a make clean to allow for external modules to be compiled with
> the existing seed and will be removed by a make mrproper or
> make distclean.
> --
> 2.17.1
>
--
Kees Cook
next prev parent reply other threads:[~2020-02-25 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 12:24 [PATCH] gcc-plugins: fix gcc-plugins directory path in documentation Masahiro Yamada
2020-02-25 18:58 ` Kees Cook [this message]
2020-06-28 5:59 ` Masahiro Yamada
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=202002251057.C4E397A@keescook \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--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;
as well as URLs for NNTP newsgroup(s).