From: Taeung Song <treeze.taeung@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH v2 0/7] perf config: Add support for config read/write
Date: Mon, 14 Nov 2016 17:46:38 +0900 [thread overview]
Message-ID: <e4ac9706-639d-015e-d751-e1ffbc7500cd@gmail.com> (raw)
In-Reply-To: <1479111702-5989-1-git-send-email-treeze.taeung@gmail.com>
Hi, Arnaldo :)
I guess you're so busy,
but would you mind If I ask a question ?
I sent a patchset adding support for config read/write.
(There are also Namhyung's demand lately
https://lkml.org/lkml/2016/10/24/572)
For a while, I stoped the patchset about default config array
https://lkml.org/lkml/2016/9/5/17 .
Is it better to handle support for config reade/write, first ?
Thanks,
Taeung
On 11/14/2016 05:21 PM, Taeung Song wrote:
> Hello, :)
>
> Add simple config read/write functionalities.
>
> I had worked at the related patchset https://lkml.org/lkml/2016/2/22/38
> But I remake new this patchset for only support for read/write config file.
> And There're Namhyung's requests https://lkml.org/lkml/2016/10/24/572
>
> In particular, I agonized implement way for write functionality.
> I especially wonder other opinions about new boolean variable
> 'from_system_config' I use.
>
> If someone review this patchset and give me some feedback,
> I'd appreciated it. :)
>
> Thanks,
> Taeung
>
> v2:
> - a bit change commit messages
> - refactor parts of parse_config_arg
>
> Taeung Song (7):
> perf config: Add support for getting functionality
> perf config: Document examples getting config info in man page
> perf config: Parse arguments before getting functionality
> perf config: Parse arguments before setting functionality
> perf config: Add support for write functionality
> perf config: Document config setting examples in man page
> perf config: Mark where are config items from (user or system)
>
> tools/perf/Documentation/perf-config.txt | 35 +++++++
> tools/perf/builtin-config.c | 155 ++++++++++++++++++++++++++++++-
> tools/perf/util/config.c | 20 ++++
> tools/perf/util/config.h | 4 +
> 4 files changed, 211 insertions(+), 3 deletions(-)
>
prev parent reply other threads:[~2016-11-14 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 8:21 Taeung Song
2016-11-14 8:21 ` [PATCH v2 1/7] perf config: Add support for getting functionality Taeung Song
2016-11-14 8:21 ` [PATCH v2 2/7] perf config: Document examples getting config info in man page Taeung Song
2016-11-14 8:21 ` [PATCH v2 3/7] perf config: Parse arguments before getting functionality Taeung Song
2016-11-14 8:21 ` [PATCH v2 4/7] perf config: Parse arguments before setting functionality Taeung Song
2016-11-14 8:21 ` [PATCH v2 5/7] perf config: Add support for write functionality Taeung Song
2016-11-14 8:21 ` [PATCH v2 6/7] perf config: Document config setting examples in man page Taeung Song
2016-11-14 8:21 ` [PATCH v2 7/7] perf config: Mark where are config items from (user or system) Taeung Song
2016-11-14 8:46 ` Taeung Song [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=e4ac9706-639d-015e-d751-e1ffbc7500cd@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--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
Powered by JetHome