All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: David Ahern <dsahern@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	acme@infradead.org, mingo@kernel.org,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	eranian@google.com, namhyung@kernel.org, jolsa@redhat.com,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 01/10] perf, tools: Add jsmn `jasmine' JSON parser
Date: Sat, 15 Mar 2014 03:27:07 +0100	[thread overview]
Message-ID: <20140315022707.GB22728@two.firstfloor.org> (raw)
In-Reply-To: <5323859B.70201@gmail.com>

On Fri, Mar 14, 2014 at 04:41:31PM -0600, David Ahern wrote:
> On 3/14/14, 3:31 PM, Andi Kleen wrote:
> >@@ -374,6 +376,8 @@ LIB_OBJS += $(OUTPUT)util/stat.o
> >  LIB_OBJS += $(OUTPUT)util/record.o
> >  LIB_OBJS += $(OUTPUT)util/srcline.o
> >  LIB_OBJS += $(OUTPUT)util/data.o
> >+LIB_OBJS += $(OUTPUT)util/jsmn.o
> >+LIB_OBJS += $(OUTPUT)util/json.o
> >
> >  LIB_OBJS += $(OUTPUT)ui/setup.o
> >  LIB_OBJS += $(OUTPUT)ui/helpline.o
> >
> 
> CONFIG driven? Allow a user to omit this.

Why? It has no external dependencies. AFAIK that's the only reason for configs.

(unless you count the commands used by the shell script, but the basic parser
works fine even without the script)

-Andi

  reply	other threads:[~2014-03-15  2:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 21:31 perf: Add support for full Intel event lists v2 Andi Kleen
2014-03-14 21:31 ` [PATCH 01/10] perf, tools: Add jsmn `jasmine' JSON parser Andi Kleen
2014-03-14 22:41   ` David Ahern
2014-03-15  2:27     ` Andi Kleen [this message]
2014-03-15 13:04       ` Arnaldo Carvalho de Melo
2014-03-15 18:04         ` Andi Kleen
2014-03-15 15:46       ` David Ahern
2014-03-14 21:31 ` [PATCH 02/10] perf, tools: Add support for text descriptions of events and alias add Andi Kleen
2014-03-14 21:31 ` [PATCH 03/10] fixup! " Andi Kleen
2014-03-14 21:31 ` [PATCH 04/10] perf, tools: Add support for reading JSON event files Andi Kleen
2014-03-14 21:31 ` [PATCH 05/10] perf, tools: Automatically look for event file name for cpu v2 Andi Kleen
2014-03-14 21:31 ` [PATCH 06/10] perf, tools: Add perf download to download event files v2 Andi Kleen
2014-03-14 21:31 ` [PATCH 07/10] perf, tools: Allow events with dot Andi Kleen
2014-03-14 21:31 ` [PATCH 08/10] perf, tools: Query terminal width and use in perf list Andi Kleen
2014-03-14 21:31 ` [PATCH 09/10] perf, tools, test: Add test case for alias and JSON parsing Andi Kleen
2014-03-14 21:31 ` [PATCH 10/10] perf, tools, record: Always allow to overide default period v2 Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2014-04-16 18:49 [PATCH 01/10] perf, tools: Add jsmn `jasmine' JSON parser Andi Kleen
2014-04-25 13:17 ` Jiri Olsa
2014-04-25 15:07   ` Andi Kleen
2014-07-30 23:22 perf: Add support for full Intel event lists v8 Andi Kleen
2014-07-30 23:22 ` [PATCH 01/10] perf, tools: Add jsmn `jasmine' JSON parser Andi Kleen
2015-05-27 21:23 [PATCH 0/10] perf: Add support for PMU events in JSON format Sukadev Bhattiprolu
2015-05-27 21:23 ` [PATCH 01/10] perf, tools: Add jsmn `jasmine' JSON parser Sukadev Bhattiprolu

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=20140315022707.GB22728@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.