From: German Rivera <German.Rivera@freescale.com>
To: Joe Perches <joe@perches.com>
Cc: <gregkh@linuxfoundation.org>, <arnd@arndb.de>,
<linux-kernel@vger.kernel.org>, <stuart.yoder@freescale.com>,
<linuxppc-release@linux.freescale.net>
Subject: Re: [RFC PATCH 1/4 v2] drivers/bus: Added Freescale Management Complex APIs
Date: Wed, 20 Aug 2014 11:20:39 -0500 [thread overview]
Message-ID: <53F4CAD7.5060904@freescale.com> (raw)
In-Reply-To: <1408497589.23250.12.camel@joe-AO725>
On 08/19/2014 08:19 PM, Joe Perches wrote:
> On Tue, 2014-08-19 at 19:54 -0500, J. German Rivera wrote:
>> 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.
> []
>> 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 | 50 +++
>
> Why should any of these files be put in include/linux?
>
These header files are going to be shared by more than one of our
drivers. Should they be in a new directory under include
(such as include/fsl/) or under include/linux (such as include/linux/fsl/)?
Thanks,
German
>
next prev parent reply other threads:[~2014-08-20 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 0:54 [RFC PATCH 0/4 v2] drivers/bus: Freescale Management Complex bus driver patch series J. German Rivera
2014-08-20 0:54 ` [RFC PATCH 1/4 v2] drivers/bus: Added Freescale Management Complex APIs J. German Rivera
2014-08-20 1:19 ` Joe Perches
2014-08-20 16:20 ` German Rivera [this message]
2014-08-20 0:54 ` [RFC PATCH 2/4 v2] drivers/bus: Freescale Management Complex (fsl-mc) bus driver J. German Rivera
2014-08-22 11:16 ` Michal Marek
2014-08-20 0:54 ` [RFC PATCH 3/4 v2] drivers/bus: Device driver for FSL-MC DPRC devices J. German Rivera
2014-08-20 0:54 ` [RFC PATCH 4/4 v2] Update MAINTAINERS file J. 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=53F4CAD7.5060904@freescale.com \
--to=german.rivera@freescale.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-release@linux.freescale.net \
--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
Powered by JetHome