From: Greg KH <gregkh@linuxfoundation.org>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: Ruxandra Ioana Radulescu <ruxandra.radulescu@nxp.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bogdan Purcareata <bogdan.purcareata@nxp.com>,
Leo Li <leoyang.li@nxp.com>,
"stuyoder@gmail.com" <stuyoder@gmail.com>,
Roy Pledge <roy.pledge@nxp.com>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Stuart Yoder <stuart.yoder@nxp.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH v4] staging: fsl-mc: move bus driver out of staging
Date: Wed, 20 Dec 2017 11:42:03 +0100 [thread overview]
Message-ID: <20171220104203.GA29824@kroah.com> (raw)
In-Reply-To: <5A3A3AE6.6080905@nxp.com>
On Wed, Dec 20, 2017 at 10:26:49AM +0000, Laurentiu Tudor wrote:
> On 12/19/2017 06:10 PM, Greg KH wrote:
> >>> But all of these .h files are only used by the code in this specific
> >>> directory, no where else.
> >>
> >> They are also used by our ethernet driver, see:
> >> drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.h
> >
> > Ick, really? Then they should not be buried in a bus-specific
> > location, but rather be in include/linux/SOMEWHERE, right?
>
> Right. The goal is that in the end, all headers be moved to the already
> existing include/linux/fsl/. For now I've left these in staging because
> they are not part of the bus "core" infrastructure.
Then shouldn't they be in the drivers/staging/fsl-mc/include/ directory
now to show this?
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-20 10:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 10:08 [PATCH v4] staging: fsl-mc: move bus driver out of staging laurentiu.tudor
2017-12-19 14:48 ` Greg KH
2017-12-19 15:21 ` Laurentiu Tudor
2017-12-19 15:29 ` Greg KH
2017-12-19 15:39 ` Laurentiu Tudor
2017-12-19 16:10 ` Greg KH
2017-12-20 10:26 ` Laurentiu Tudor
2017-12-20 10:42 ` Greg KH [this message]
2017-12-20 10:52 ` Laurentiu Tudor
2017-12-20 11:06 ` Greg KH
2017-12-20 11:52 ` Laurentiu Tudor
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=20171220104203.GA29824@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@lunn.ch \
--cc=bogdan.purcareata@nxp.com \
--cc=devel@driverdev.osuosl.org \
--cc=jason@lakedaemon.net \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=roy.pledge@nxp.com \
--cc=ruxandra.radulescu@nxp.com \
--cc=stuart.yoder@nxp.com \
--cc=stuyoder@gmail.com \
--cc=tglx@linutronix.de \
/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