From: Matthias Kaehlcke <mka@chromium.org>
To: Michal Marek <mmarek@suse.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
"H . J . Lu" <hjl.tools@gmail.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"X86 ML" <x86@kernel.org>,
"Linux Kbuild mailing list" <linux-kbuild@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Michael Davidson" <md@google.com>,
"Greg Hackmann" <ghackmann@google.com>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Stephen Hines" <srhines@google.com>,
"Kees Cook" <keescook@chromium.org>,
"Bernhard Rosenkränzer" <Bernhard.Rosenkranzer@linaro.org>,
"Peter Foley" <pefoley2@pefoley.com>,
"Behan Webster" <behanw@converseincode.com>,
"Douglas Anderson" <dianders@chromium.org>
Subject: Re: [PATCH v2 1/4] kbuild: Add cc-option-raw macro
Date: Wed, 14 Jun 2017 09:38:13 -0700 [thread overview]
Message-ID: <20170614163813.GM141096@google.com> (raw)
In-Reply-To: <fd23743c-93a1-a5e2-dd70-c46b07032cfd@suse.com>
El Wed, Jun 14, 2017 at 10:32:20AM +0200 Michal Marek ha dit:
> Dne 14.6.2017 v 09:31 Arnd Bergmann napsal(a):
> > On Wed, Jun 14, 2017 at 3:27 AM, Masahiro Yamada
> > <yamada.masahiro@socionext.com> wrote:
> >> 2017-06-14 8:08 GMT+09:00 Matthias Kaehlcke <mka@chromium.org>:
> >>> cc-option uses KBUILD_CFLAGS and KBUILD_CPPFLAGS when it determines
> >>> whether an option is supported or not. This is fine for options used to
> >>> build the kernel itself, however some components like the x86 boot code
> >>> use a different set of flags.
> >>>
> >>> Add the new macro cc-option-raw which serves the same purpose as
> >>> cc-option but has additional parameters. One parameter is the compiler
> >>> with which the check should be performed, the other the compiler options
> >>> to be used instead KBUILD_C*FLAGS. The compiler parameter allows other
> >>> macros like hostcc-option to be implemented on top of cc-option-raw.
> >>>
> >>> Also rework cc-option to make use of cc-option-raw.
> >>>
> >>> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> >>> Suggested-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> >>> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> >>> ---
> >>> Changes in v2:
> >>> - Changed macro name from Add cc-option-no-kbuild to cc-option-raw
> >>> - Added compiler as parameter to the macro
> >>> - Reworked cc-option to make use of cc-option-raw
> >>> - Updated commit message
> >>>
> >>> scripts/Kbuild.include | 9 +++++++--
> >>> 1 file changed, 7 insertions(+), 2 deletions(-)
> >>>
> >>
> >> Acked-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> >> (if nothing better pops up)
> >
> > Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> Acked-by: Michal Marek <mmarek@suse.com>
>
>
> > Regarding the naming, __cc-option might be better than cc-option-raw,
> > but the current version is fine too.
>
> I have no strong opinion either way :).
I'm going to change it to __cc-option since there is a slight
preference for it and I have to respin the series anyway. I'll wait
a bit for feedback from the x86 folks before sending the new version.
next prev parent reply other threads:[~2017-06-14 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 23:08 [PATCH v2 0/4] x86: stack alignment for boot code and clang Matthias Kaehlcke
2017-06-13 23:08 ` [PATCH v2 1/4] kbuild: Add cc-option-raw macro Matthias Kaehlcke
2017-06-14 1:27 ` Masahiro Yamada
2017-06-14 7:31 ` Arnd Bergmann
2017-06-14 7:44 ` Masahiro Yamada
2017-06-14 8:32 ` Michal Marek
2017-06-14 16:38 ` Matthias Kaehlcke [this message]
2017-06-13 23:08 ` [PATCH v2 2/4] kbuild: Add hostcc-option macro Matthias Kaehlcke
2017-06-14 1:28 ` Masahiro Yamada
2017-06-14 7:26 ` Arnd Bergmann
2017-06-14 7:40 ` Masahiro Yamada
2017-06-13 23:08 ` [PATCH v2 3/4] x86/build: Use cc-option-raw for boot code compiler options Matthias Kaehlcke
2017-06-13 23:08 ` [PATCH v2 4/4] x86/build: Specify stack alignment for clang Matthias Kaehlcke
2017-06-14 1:30 ` [PATCH v2 0/4] x86: stack alignment for boot code and clang 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=20170614163813.GM141096@google.com \
--to=mka@chromium.org \
--cc=Bernhard.Rosenkranzer@linaro.org \
--cc=arnd@arndb.de \
--cc=behanw@converseincode.com \
--cc=dianders@chromium.org \
--cc=dwmw2@infradead.org \
--cc=ghackmann@google.com \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=md@google.com \
--cc=mingo@redhat.com \
--cc=mmarek@suse.com \
--cc=ndesaulniers@google.com \
--cc=pefoley2@pefoley.com \
--cc=srhines@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.