From: Scott Wood <scottwood@freescale.com>
To: Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Cc: Phillips Kim-R1AAHA <Kim.Phillips@freescale.com>,
Alexander Graf <agraf@suse.de>,
Rivera Jose-B46482 <German.Rivera@freescale.com>,
<gregkh@linuxfoundation.org>, <arnd@arndb.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] drivers/bus: Added Freescale Management Complex APIs
Date: Thu, 18 Sep 2014 18:29:06 -0500 [thread overview]
Message-ID: <1411082946.13320.29.camel@snotra.buserror.net> (raw)
In-Reply-To: <581cd5a2ba854ef883ba488cec70ad62@CY1PR0301MB0748.namprd03.prod.outlook.com>
On Thu, 2014-09-18 at 18:13 -0500, Yoder Stuart-B08248 wrote:
>
> > -----Original Message-----
> > From: Kim Phillips [mailto:kim.phillips@freescale.com]
> > Sent: Thursday, September 18, 2014 3:23 PM
> > To: Alexander Graf
> > Cc: Rivera Jose-B46482; <gregkh@linuxfoundation.org>; <arnd@arndb.de>; <linux-kernel@vger.kernel.org>; Yoder
> > Stuart-B08248; Wood Scott-B07421; <linuxppc-release@linux.freescale.net>
> > Subject: Re: [PATCH 1/4] drivers/bus: Added Freescale Management Complex APIs
> >
> > On Thu, 18 Sep 2014 15:14:03 +0200
> > Alexander Graf <agraf@suse.de> wrote:
> >
> > > > Am 18.09.2014 um 06:17 schrieb German Rivera <German.Rivera@freescale.com>:
> > > >
> > > >> On 09/15/2014 06:44 PM, Kim Phillips wrote:
> > > >> On Thu, 11 Sep 2014 12:34:21 -0500
> > > >> "J. German Rivera" <German.Rivera@freescale.com> wrote:
> > > >>
> > > >>> From: "J. German Rivera" <German.Rivera@freescale.com>
> > > >>>
> > > >>> APIs to access the Management Complex (MC) hardware
> > > >>> module of Freescale LS2 SoCs. This patch includes
> > > >>> APIs to check the MC firmware version and to manipulate
> > > >>> DPRC objects in the MC.
> > > >>>
> > > >>> Signed-off-by: J. German Rivera <German.Rivera@freescale.com>
> > > >>> Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
> > > >>> ---
> > > >>> drivers/bus/fsl-mc/dpmng.c | 93 +++++
> > > >>> drivers/bus/fsl-mc/dprc.c | 504 +++++++++++++++++++++++
> > > >>> drivers/bus/fsl-mc/fsl_dpmng_cmd.h | 83 ++++
> > > >>> drivers/bus/fsl-mc/fsl_dprc_cmd.h | 545 +++++++++++++++++++++++++
> > > >>> drivers/bus/fsl-mc/fsl_mc_sys.c | 237 +++++++++++
> > > >>> include/linux/fsl_dpmng.h | 120 ++++++
> > > >>> include/linux/fsl_dprc.h | 790 ++++++++++++++++++++++++++++++++++++
> > > >>> include/linux/fsl_mc_cmd.h | 182 +++++++++
> > > >>> include/linux/fsl_mc_sys.h | 81 ++++
> > > >>> 9 files changed, 2635 insertions(+)
> > > >>> create mode 100644 drivers/bus/fsl-mc/dpmng.c
> > > >>> create mode 100644 drivers/bus/fsl-mc/dprc.c
> > > >>> create mode 100644 drivers/bus/fsl-mc/fsl_dpmng_cmd.h
> > > >>> create mode 100644 drivers/bus/fsl-mc/fsl_dprc_cmd.h
> > > >>> create mode 100644 drivers/bus/fsl-mc/fsl_mc_sys.c
> > > >>> create mode 100644 include/linux/fsl_dpmng.h
> > > >>> create mode 100644 include/linux/fsl_dprc.h
> > > >>> create mode 100644 include/linux/fsl_mc_cmd.h
> > > >>> create mode 100644 include/linux/fsl_mc_sys.h
> > > >>
> > > >> the fsl prefix in the filename fsl_dpmng_cmd.h is redundant with
> > > >> its directory name fsl-mc/. Note that I find dashes ('-') in
> > > >> filenames make them easier to type: is there a reason we're using
> > > >> underscores here?
> > > > This is a convention that we decided early on '-' for directory names
> > > > and '_' for file names.
> >
> > based on what?
>
> We looked at how generally files were named in kernel source.
>
> For what it's worth in my 3.16 branch:
>
> $ find drivers/ -type f | grep '-' | wc -l
> 4308
> $ find drivers/ -type f | grep '_' | wc -l
> 6507
>
> ...it seems that there are far more files named with underscores. If Greg
> or Arnd wants the files renamed, fine, but other than that I see no reason
> to change this.
60% isn't "far more". Regardless of whether we change this (dashes are
easier to read, easier to type, and are what English normally uses --
underscores are for when you can't use a dash for technical reasons),
let's not start making rules based on weak statistical inferences.
Plus, why limit the search to drivers? E.g. if you looked at arch/
you'd reach the opposite conclusion.
-Scott
next prev parent reply other threads:[~2014-09-18 23:29 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 17:34 [PATCH 0/4] drivers/bus: Freescale Management Complex bus driver patch series J. German Rivera
2014-09-11 17:34 ` [PATCH 1/4] drivers/bus: Added Freescale Management Complex APIs J. German Rivera
2014-09-11 18:45 ` Joe Perches
2014-09-17 16:35 ` German Rivera
2014-09-15 23:44 ` Kim Phillips
2014-09-16 4:31 ` Scott Wood
2014-09-16 19:28 ` Kim Phillips
2014-09-16 19:58 ` Scott Wood
2014-09-18 4:17 ` German Rivera
2014-09-18 13:14 ` Alexander Graf
2014-09-18 20:22 ` Kim Phillips
2014-09-18 23:03 ` Scott Wood
2014-09-18 23:13 ` Stuart Yoder
2014-09-18 23:29 ` Scott Wood [this message]
2014-09-18 23:46 ` Stuart Yoder
2014-09-19 3:05 ` German Rivera
2014-09-19 17:19 ` Kim Phillips
2014-09-19 19:06 ` Stuart Yoder
2014-09-19 20:24 ` Kim Phillips
2014-09-19 20:32 ` Alexander Graf
2014-09-19 20:41 ` Scott Wood
2014-09-19 21:46 ` Alexander Graf
2014-09-20 15:36 ` Stuart Yoder
2014-09-19 21:37 ` Stuart Yoder
2014-09-19 21:30 ` Stuart Yoder
2014-09-19 0:18 ` Stuart Yoder
2014-09-19 2:34 ` German Rivera
2014-09-19 18:25 ` Stuart Yoder
2014-09-19 20:58 ` Kim Phillips
2014-09-22 14:42 ` Stuart Yoder
2014-09-22 14:57 ` <gregkh@linuxfoundation.org>
2014-09-22 15:01 ` Stuart Yoder
2014-09-18 23:39 ` Stuart Yoder
2014-09-18 23:53 ` Scott Wood
2014-09-11 17:34 ` [PATCH 2/4] drivers/bus: Freescale Management Complex (fsl-mc) bus driver J. German Rivera
2014-09-11 18:49 ` Joe Perches
2014-09-17 23:50 ` German Rivera
2014-09-11 17:34 ` [PATCH 3/4] drivers/bus: Device driver for FSL-MC DPRC devices J. German Rivera
2014-09-11 17:34 ` [PATCH 4/4] Update MAINTAINERS file J. German Rivera
2014-09-15 23:44 ` [PATCH 0/4] drivers/bus: Freescale Management Complex bus driver patch series Kim Phillips
2014-09-18 0:20 ` German Rivera
2014-09-18 12:58 ` Alexander Graf
2014-09-19 0:31 ` German Rivera
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=1411082946.13320.29.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=German.Rivera@freescale.com \
--cc=Kim.Phillips@freescale.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart.yoder@freescale.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
all inboxes | Powered by JetHome®