From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
linux-hardening@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Frank Eigler <fche@redhat.com>,
Justin Forbes <jforbes@redhat.com>,
Ondrej Mosnacek <omosnace@redhat.com>
Subject: Re: [PATCH] kbuild: rebuild GCC plugins when the compiler is upgraded
Date: Thu, 18 Mar 2021 12:57:21 -0500 [thread overview]
Message-ID: <20210318175721.basitauxxboywjsx@treble> (raw)
In-Reply-To: <CAK7LNAQDbhzi5s8iaqVSV82v8n-+0a=XB3-8wg=Nu41XyRETvw@mail.gmail.com>
On Wed, Mar 10, 2021 at 10:44:46PM +0900, Masahiro Yamada wrote:
> > Masahiro,
> >
> > Ping. Do you have a better approach for building GCC plugins in the
> > external module directory?
>
>
> I am not sure if building GCC plugins in the external module directory
> is the right approach.
I'm certainly open to any better ideas that would allow GCC plugins to
be enabled in distro kernel builds.
--
Josh
prev parent reply other threads:[~2021-03-18 17:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 11:37 [PATCH] kbuild: rebuild GCC plugins when the compiler is upgraded Masahiro Yamada
2021-03-04 23:20 ` Kees Cook
2021-03-04 23:37 ` Linus Torvalds
2021-03-05 2:25 ` Josh Poimboeuf
2021-03-06 1:28 ` Josh Poimboeuf
2021-03-06 2:18 ` Masahiro Yamada
2021-03-06 2:50 ` Josh Poimboeuf
2021-03-09 20:31 ` Josh Poimboeuf
2021-03-10 13:44 ` Masahiro Yamada
2021-03-18 17:57 ` Josh Poimboeuf [this message]
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=20210318175721.basitauxxboywjsx@treble \
--to=jpoimboe@redhat.com \
--cc=fche@redhat.com \
--cc=jforbes@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@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=omosnace@redhat.com \
--cc=torvalds@linux-foundation.org \
/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