From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
linux-kernel@vger.kernel.org,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 1/5] perf tools: Factor ui_browser ops out of ui_browser struct
Date: Fri, 20 Jun 2014 08:33:52 +0900 [thread overview]
Message-ID: <87vbrw79un.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20140619164921.GA31520@krava.brq.redhat.com> (Jiri Olsa's message of "Thu, 19 Jun 2014 18:49:21 +0200")
Hi Jiri,
On Thu, 19 Jun 2014 18:49:21 +0200, Jiri Olsa wrote:
> On Thu, Jun 19, 2014 at 12:38:51PM -0300, Arnaldo Carvalho de Melo wrote:
>> Em Thu, Jun 19, 2014 at 01:41:12PM +0200, Jiri Olsa escreveu:
>> > Separating ops out of 'struct ui_browser' into
>> > 'struct ui_browser_ops'.
>>
>> You stated what you did, and that helps in understanding what this patch
>> is about, now we only need to have a paragraph on _why_ this is needed
>> :-)
>
> well.. it's not ;-) but we always separated ops from the
> structs IIRC
>
> I introduced another callback in the early stage of this change,
> but replaced it later.. this remained ;-)
>
> no need to take it.. as I wrote in patch 0:
>
> Patches 1 and 2 are not necessary for the functionality,
> they are just byproducts of another early way I tried,
> but I think they could go in.
Hmm.. I think it should make the ops const, otherwise it makes only a
little sense.
[SNIP]
>> > +static bool ui_browser__filter(struct ui_browser *browser, void *entry)
>> > +{
>> > + return browser->ops.filter ? browser->ops.filter(browser, entry) :
>> > + false;
>> > +}
>> > +
>> > static struct list_head *
>> > ui_browser__list_head_filter_entries(struct ui_browser *browser,
>> > struct list_head *pos)
>> > {
>> > do {
>> > - if (!browser->filter || !browser->filter(browser, pos))
>> > + if (!ui_browser__filter(browser, pos))
Looks like this can be a separate cleanup.
Thanks,
Namhyung
>> > return pos;
>> > pos = pos->next;
>> > } while (pos != browser->entries);
next prev parent reply other threads:[~2014-06-19 23:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 11:41 [PATCHv2 0/5] perf tools tui: Display columns headers Jiri Olsa
2014-06-19 11:41 ` [PATCH 1/5] perf tools: Factor ui_browser ops out of ui_browser struct Jiri Olsa
2014-06-19 15:38 ` Arnaldo Carvalho de Melo
2014-06-19 16:49 ` Jiri Olsa
2014-06-19 23:33 ` Namhyung Kim [this message]
2014-06-19 11:41 ` [PATCH 2/5] perf tools: Remove ev_name argument from perf_evsel__hists_browse Jiri Olsa
2014-06-19 15:41 ` Arnaldo Carvalho de Melo
2014-06-25 5:51 ` [tip:perf/core] perf hists browser: " tip-bot for Jiri Olsa
2014-06-19 11:41 ` [PATCH 3/5] perf tools: Fix scrollbar refresh row index Jiri Olsa
2014-06-25 5:51 ` [tip:perf/core] perf ui browser: " tip-bot for Jiri Olsa
2014-06-19 11:41 ` [PATCH 4/5] perf tools tui: Display columns header text on 'H' press Jiri Olsa
2014-06-19 11:41 ` [PATCH 5/5] perf tools: Add report.show-headers config file option Jiri Olsa
2014-06-19 12:56 ` Namhyung Kim
2014-06-19 13:02 ` Jiri Olsa
2014-06-19 13:09 ` Namhyung Kim
2014-06-19 16:51 ` Jiri Olsa
2014-06-19 23:37 ` Namhyung Kim
2014-06-19 15:28 ` Arnaldo Carvalho de Melo
2014-06-19 16:58 ` Jiri Olsa
2014-06-19 23:46 ` Namhyung Kim
2014-06-20 8:03 ` Jiri Olsa
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=87vbrw79un.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
/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