From: Jiri Olsa <jolsa@redhat.com>
To: "Wangnan (F)" <wangnan0@huawei.com>
Cc: acme@redhat.com, linux-kernel@vger.kernel.org, pi3orama@163.com,
lizefan@huawei.com, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH] tools build: Remove FEATURE-DUMP
Date: Fri, 18 Dec 2015 11:13:24 +0100 [thread overview]
Message-ID: <20151218101324.GB670@krava.brq.redhat.com> (raw)
In-Reply-To: <5673C6A1.2090109@huawei.com>
On Fri, Dec 18, 2015 at 04:41:05PM +0800, Wangnan (F) wrote:
SNIP
> >> # features detection state.
> >> FEATURE_INCLUDE_FILENAME = $(OUTPUT)FEATURE-INCLUDE$(FEATURE_USER)
> >>+FEATURE_DUMP := $(foreach feat,$(FEATURE_DISPLAY),feature-$(feat)=$(feature-$(feat)))
> >>+FEATURE_DUMP_FILE := $(foreach feat,$(FEATURE_DISPLAY),$(shell touch $(FEATURE_INCLUDE_FILENAME); cat $(FEATURE_INCLUDE_FILENAME) | grep 'feature-$(feat)='))
> >hum, this ignores dwarf-post-unwind setup, I think it needs more changes
> >I'll post new version
>
> Hi Jiri,
>
> What the current status of this patch and 'tools build: Introduce
> features dump include makefile'? They are in my local tree for a long time.
hi,
I'll try to send it out next week.. I needed to factor the code a little
jirka
prev parent reply other threads:[~2015-12-18 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 9:06 [PATCH 1/2] tools build: Introduce features dump include makefile Jiri Olsa
2015-11-27 9:06 ` [PATCH 2/2] perf build: Use FEATURE-INCLUDE in bpf subproject Jiri Olsa
2015-12-07 8:56 ` [PATCH 1/2] tools build: Introduce features dump include makefile Jiri Olsa
2015-12-07 9:22 ` Wangnan (F)
2015-12-07 10:29 ` Jiri Olsa
2015-12-07 10:32 ` Wangnan (F)
2015-12-07 10:38 ` Wangnan (F)
2015-12-07 10:48 ` [PATCH] tools build: Remove FEATURE-DUMP Wang Nan
2015-12-07 13:52 ` Jiri Olsa
2015-12-18 8:41 ` Wangnan (F)
2015-12-18 10:13 ` Jiri Olsa [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=20151218101324.GB670@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.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).