All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
	Andi Kleen <andi@firstfloor.org>, Jiri Olsa <jolsa@kernel.org>,
	Wang Nan <wangnan0@huawei.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Vendor events file/dir names
Date: Wed, 19 Oct 2016 17:24:12 +0200	[thread overview]
Message-ID: <20161019152412.GA3112@gmail.com> (raw)
In-Reply-To: <20161019140757.GC25522@kernel.org>


* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:

> Em Wed, Oct 19, 2016 at 03:38:33PM +0200, Ingo Molnar escreveu:
> > * Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > > Em Tue, Oct 18, 2016 at 09:59:01AM +0200, Ingo Molnar escreveu:
> > > > * Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > > > > 	Ingo pointed out to me that in the kernel sources we do not use
> > > > > file/dir names with uppercase chars (look, for instance, at arch/), so I
> > > > > mostly scripted a conversion to lowercase and what I got is at:
> > > 
> > > > >    git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/vendor_events
> > > 
> > > > > 	Please let me know if you have any technical argument against
> > > > > this move,
> > > > 
> > > > Looks good to me!
> > > 
> > > So I've made this signed tag available with just what is in this branch,
> > > that was based off tip/perf/urgent, please pull it into the most convenient
> > > branch at this time,
> > > 
> > > Thanks,
> > > 
> > > - Arnaldo
> > > 
> > > tag perf-vendor_events-for-mingo-20161018
> > 
> > Ok, I tried this out, and I like it mostly - the event files hierarchy looks good 
> > and the 'perf list' output looks good, but I found a couple of usability problems 
> > when trying to actually navigate and search the new hw events:
> 
> Ok, but can't we work on these usability glitches with patches on top of
> what we have now?

Yeah, sure - and it seems like we are in agreement about the usability details, so 
I've pulled your branch into tip:perf/core.

Thanks,

	Ingo

  reply	other threads:[~2016-10-19 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 19:04 [RFC] Vendor events file/dir names Arnaldo Carvalho de Melo
2016-10-17 21:26 ` Andi Kleen
2016-10-18  7:59 ` Ingo Molnar
2016-10-18 15:36   ` [GIT PULL] " Arnaldo Carvalho de Melo
2016-10-19 13:38     ` Ingo Molnar
2016-10-19 14:07       ` Arnaldo Carvalho de Melo
2016-10-19 15:24         ` Ingo Molnar [this message]
2016-10-19 16:41       ` Andi Kleen
2016-10-19 17:49         ` Andi Kleen

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=20161019152412.GA3112@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=sukadev@linux.vnet.ibm.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 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.