From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [tree] ftrace, v16
Date: Thu, 12 Jun 2008 11:18:18 +0200 [thread overview]
Message-ID: <20080612091818.GD15312@elte.hu> (raw)
In-Reply-To: <20080612083339.GA25565@uranus.ravnborg.org>
* Sam Ravnborg <sam@ravnborg.org> wrote:
> Hi Ingo
>
> > kbuild: create new CFLAGS_REMOVE_(basename).o option
>
> But no changes to Documentation/kbuild/makefiles.txt
>
> Documentation must be included for new kbuild features.
>
>
> > +ifdef CONFIG_DYNAMIC_FTRACE
> > +CFLAGS_REMOVE_ftrace.o = -pg
> > +endif
>
> I can see where this comes from as we have:
>
> CFLAGS_ftrace.o := -foobar
>
> But in all cases below I see the pattern:
>
> ifdef CONFIG_FOO_BAR
> CFLAGS_REMOVE_foobar.o = -pg
> endif
>
> And it would be nice to get this on one line instead.
> And use a syntax we can somehow remember.
>
> Today we have:
> ccflags-y := -foobar
>
> to add options valid for the whole file.
> So we should then add:
> - possibility to remove an option valid for the whole file
> - add/remove an option for a single file
>
> The suggested syntax:
> ccflags-remove-y := -foobar
> ccflags-<file.o>-y := -foobar
> ccflags-remove-<file.o>-y := -foobar
>
> So in the case above for ftrace we would use:
>
> ccflags-remove-ftrace.o-$(CONFIG_DYNAMIC_FTRACE) := -pg
>
> Comments?
sounds like a good cleanup to me. Would you be interested in sending
patches for this?
Ingo
next prev parent reply other threads:[~2008-06-12 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 7:54 [tree] ftrace, v16 Ingo Molnar
2008-06-12 7:55 ` Ingo Molnar
2008-06-12 8:33 ` Sam Ravnborg
2008-06-12 9:18 ` Ingo Molnar [this message]
2008-06-12 13:24 ` Sam Ravnborg
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=20080612091818.GD15312@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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