From: Namhyung Kim <namhyung@kernel.org>
To: Taewoong Song <treeze.taeung@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jolsa@redhat.com
Subject: Re: [PATCH 2/2] perf tools: Add a option 'remove' to perf-config and features which get or set a config variable.
Date: Sun, 19 Apr 2015 12:42:02 +0900 [thread overview]
Message-ID: <20150419034202.GC10169@danjae.kornet> (raw)
In-Reply-To: <6F8981BC-A058-4D84-93FC-B7CB8ADDCC53@gmail.com>
On Sat, Apr 18, 2015 at 02:02:17PM +0900, Taewoong Song wrote:
> > On Apr 13, 2015, at 3:55 PM, Namhyung Kim <namhyung@kernel.org> wrote:
> > On Sun, Apr 12, 2015 at 11:44:49PM +0900, Taeung Song wrote:
> >> +static struct config_section *find_config_section(const char *section_name)
> >> +{
> >> + struct config_section *section_node;
> >
> > It'd be better to split declaration and function body with a blank line.
> >
>
> Does mean it like followed by ?
>
> +static struct config_section *find_config_section(const char *section_name)
> +
> +{
> + struct config_section *section_node;
>
> ,or is it ?
>
> +static struct config_section *find_config_section(const char *section_name)
> +{
> +
> + struct config_section *section_node;
Nope! I meant
static struct config_section *find_config_section(const char *section_name)
{
struct config_section *section node
<-- here
list_for_each_entry(section_node, §ions, list)
...
}
>
> >
> >> + list_for_each_entry(section_node, §ions, list)
> >> + if (!strcmp(section_node->name, section_name))
> >> + return section_node;
> >> +
> >> + return NULL;
> >> +}
> >> +
> >> +static struct config_element *find_config_element(const char *subkey
> >> + , struct config_section *section_node)
And this is not how we put comma, please change it to
static struct config_element *find_config_element(const char *subkey,
struct config_section *section_node)
Ditto for others..
Thanks,
Namhyung
next prev parent reply other threads:[~2015-04-19 3:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 14:44 [PATCH 1/2] perf tools: Add 'perf-config' command Taeung Song
2015-04-12 14:44 ` [PATCH 2/2] perf tools: Add a option 'remove' to perf-config and features which get or set a config variable Taeung Song
2015-04-13 6:55 ` Namhyung Kim
[not found] ` <6F8981BC-A058-4D84-93FC-B7CB8ADDCC53@gmail.com>
2015-04-19 3:42 ` Namhyung Kim [this message]
2015-04-13 6:16 ` [PATCH 1/2] perf tools: Add 'perf-config' command Namhyung Kim
[not found] ` <5CB87CAF-B6EE-4AE0-BC3C-45CEF14C28EC@gmail.com>
2015-04-19 3:27 ` Namhyung Kim
[not found] ` <70EA4387-5059-4026-8819-039474865EEE@gmail.com>
2015-04-19 3:34 ` Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2015-04-09 14:26 Taeung Song
2015-04-09 14:26 ` [PATCH 2/2] perf tools: Add a option 'remove' to perf-config and features which get or set a config variable Taeung Song
2015-04-10 9:31 ` Jiri Olsa
2015-04-12 14:45 ` Taewoong Song
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=20150419034202.GC10169@danjae.kornet \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=treeze.taeung@gmail.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