All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
	Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@kernel.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: [RFC] Vendor events file/dir names
Date: Mon, 17 Oct 2016 16:04:38 -0300	[thread overview]
Message-ID: <20161017190438.GU12815@kernel.org> (raw)

Hi,

	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
   
   https://git.kernel.org/cgit/linux/kernel/git/acme/linux.git/log/?h=perf/vendor_events

	I did test it on my Lenovo t450s (Broadwell) and got the same
results as before, and the changed file and directory names don't get
presented to the user AFAIK, so its just a matter of consistency with
the existing practices in the kernel sources, no visible difference to
users.

	Please let me know if you have any technical argument against
this move,

Thanks,

- Arnaldo

             reply	other threads:[~2016-10-17 19:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 19:04 Arnaldo Carvalho de Melo [this message]
2016-10-17 21:26 ` [RFC] Vendor events file/dir names 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
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=20161017190438.GU12815@kernel.org \
    --to=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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.