From: German Rivera <German.Rivera@freescale.com>
To: Yoder Stuart-B08248 <stuart.yoder@freescale.com>,
Phillips Kim-R1AAHA <Kim.Phillips@freescale.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wood Scott-B07421 <scottwood@freescale.com>,
"agraf@suse.de" <agraf@suse.de>,
"linuxppc-release@linux.freescale.net"
<linuxppc-release@linux.freescale.net>,
Erez Nir-RM30794 <nir.erez@freescale.com>
Subject: Re: [PATCH 0/3 v2] drivers/bus: Freescale Management Complex bus driver patch series
Date: Tue, 23 Sep 2014 09:52:33 -0500 [thread overview]
Message-ID: <54218931.5070808@freescale.com> (raw)
In-Reply-To: <0e13cde24a284873ab6f65f7e5ffdb3e@CY1PR0301MB0748.namprd03.prod.outlook.com>
On 09/22/2014 12:59 PM, Yoder Stuart-B08248 wrote:
>
>
>> -----Original Message-----
>> From: Kim Phillips [mailto:kim.phillips@freescale.com]
>> Sent: Monday, September 22, 2014 11:53 AM
>> To: Rivera Jose-B46482
>> Cc: gregkh@linuxfoundation.org; arnd@arndb.de; linux-kernel@vger.kernel.org; Yoder Stuart-B08248; Wood Scott-
>> B07421; agraf@suse.de; linuxppc-release@linux.freescale.net
>> Subject: Re: [PATCH 0/3 v2] drivers/bus: Freescale Management Complex bus driver patch series
>>
>> On Fri, 19 Sep 2014 17:49:38 -0500
>> "J. German Rivera" <German.Rivera@freescale.com> wrote:
>>
>>> CHANGE HISTORY
>>>
>>> Issues pending resolution not addressed by v2:
>>> - What to do with Doxygen comments in patch 1
>>
>> It's clear they should be removed.
>>
>>> - Whether to move or not FSL-specific header files added in include/linux,
>>> by this patch series, to another location
>>
>> there wasn't a valid objection against moving them under fsl/ and
>> changing them to use dashes instead of underscores, was there?
>
> There was no objection, but here is the observation. The current
> convention seems to be that under include/linux are 'subsystem'
> types--
> include/linux/mmc
> include/linux/spi
> include/linux/raid
> etc
>
> There is no other "company" that has an include/linux/[company-name] that I can
> see. Freescale seems to be the only one. And there is only a single driver
> in there. So it looks like a complete anomaly.
>
> Why is that?
>
> I guess we could try moving our stuff to incluce/linux/fsl and see if there is
> any negative feedback on it.
>
Ok, unless there is any objection, we will do the following file renamings:
Patch 1/3
drivers/bus/fsl-mc/fsl_dpmng_cmd.h -> drivers/bus/fsl-mc/dpmng-cmd.h
drivers/bus/fsl-mc/fsl_dprc_cmd.h -> drivers/bus/fsl-mc/dprc-cmd.h
drivers/bus/fsl-mc/fsl_mc_sys.c -> drivers/bus/fsl-mc/mc-sys.c
include/linux/fsl_dpmng.h -> include/linux/fsl/dpmng.h
include/linux/fsl_dprc.h -> include/linux/fsl/dprc.h
include/linux/fsl_mc_cmd.h -> include/linux/fsl/mc-cmd.h
include/linux/fsl_mc_sys.h -> include/linux/fsl/mc-sys.h
Patch 2/3
drivers/bus/fsl-mc/fsl_mc_bus.c -> drivers/bus/fsl-mc/mc-bus.c
include/linux/fsl_mc.h -> include/linux/fsl/mc.h
include/linux/fsl_mc_private.h -> include/linux/fsl/mc-private.h
Patch 3/3
drivers/bus/fsl-mc/fsl_mc_dprc.c -> drivers/bus/fsl-mc/dprc-driver.c
(there is a file already named drivers/bus/fsl-mc/dprc.c)
> Stuart
>
prev parent reply other threads:[~2014-09-23 14:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 22:49 [PATCH 0/3 v2] drivers/bus: Freescale Management Complex bus driver patch series J. German Rivera
2014-09-19 22:49 ` [PATCH 1/3 v2] drivers/bus: Added Freescale Management Complex APIs J. German Rivera
2014-09-24 0:49 ` Kim Phillips
2014-09-25 2:23 ` German Rivera
2014-09-25 3:40 ` Kim Phillips
2014-09-25 15:44 ` German Rivera
2014-09-25 16:16 ` Scott Wood
2014-09-25 16:44 ` German Rivera
2014-09-25 20:05 ` Scott Wood
2014-09-19 22:49 ` [PATCH 2/3 v2] drivers/bus: Freescale Management Complex (fsl-mc) bus driver J. German Rivera
2014-09-19 22:49 ` [PATCH 3/3 v2] drivers/bus: Device driver for FSL-MC DPRC devices J. German Rivera
2014-10-01 2:19 ` Timur Tabi
2014-10-01 2:27 ` Scott Wood
2014-10-01 2:35 ` Timur Tabi
2014-10-02 16:36 ` German Rivera
2014-10-02 17:19 ` Timur Tabi
2014-09-22 16:53 ` [PATCH 0/3 v2] drivers/bus: Freescale Management Complex bus driver patch series Kim Phillips
2014-09-22 17:59 ` Stuart Yoder
2014-09-22 22:03 ` Kim Phillips
2014-09-23 14:52 ` German Rivera [this message]
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=54218931.5070808@freescale.com \
--to=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=linuxppc-release@linux.freescale.net \
--cc=nir.erez@freescale.com \
--cc=scottwood@freescale.com \
--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