From: Steven Rostedt <rostedt@goodmis.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-kbuild@vger.kernel.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
linuxppc-dev@lists.ozlabs.org, Ingo Molnar <mingo@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Sami Tolvanen <samitolvanen@google.com>,
Rich Felker <dalias@libc.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kbuild: introduce ccflags-remove-y and asflags-remove-y
Date: Sun, 28 Jun 2020 15:07:55 -0400 [thread overview]
Message-ID: <20200628150755.523fbb2c@oasis.local.home> (raw)
In-Reply-To: <20200628015041.1000002-1-masahiroy@kernel.org>
On Sun, 28 Jun 2020 10:50:41 +0900
Masahiro Yamada <masahiroy@kernel.org> wrote:
> CFLAGS_REMOVE_<file>.o works per object, that is, there is no
> convenient way to filter out flags for every object in a directory.
>
> Add ccflags-remove-y and asflags-remove-y to make it easily.
>
> Use ccflags-remove-y to clean up some Makefiles.
>
> Suggested-by: Sami Tolvanen <samitolvanen@google.com>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
Nice feature!
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2020-06-28 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 1:50 [PATCH] kbuild: introduce ccflags-remove-y and asflags-remove-y Masahiro Yamada
2020-06-28 19:07 ` Steven Rostedt [this message]
2020-06-29 5:57 ` Michael Ellerman
2020-06-30 2:08 ` Masahiro Yamada
2020-07-06 11:24 ` Anders Roxell
2020-07-06 12:00 ` Anders Roxell
2020-07-06 18:14 ` Masahiro Yamada
2020-07-05 7:58 ` [kbuild] fbb020c0d4: WARNING:at_kernel/trace/trace.c:#run_tracer_selftest kernel test robot
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=20200628150755.523fbb2c@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=dalias@libc.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=samitolvanen@google.com \
--cc=ysato@users.sourceforge.jp \
/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).