[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5A3A4103.6050502@nxp.com>
Date: Wed, 20 Dec 2017 10:52:52 +0000
From: Laurentiu Tudor <laurentiu.tudor@....com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: Ruxandra Ioana Radulescu <ruxandra.radulescu@....com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Bogdan Purcareata" <bogdan.purcareata@....com>,
Leo Li <leoyang.li@....com>,
"stuyoder@...il.com" <stuyoder@...il.com>,
Roy Pledge <roy.pledge@....com>,
"andrew@...n.ch" <andrew@...n.ch>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Stuart Yoder <stuart.yoder@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Marc Zyngier <marc.zyngier@....com>
Subject: Re: [PATCH v4] staging: fsl-mc: move bus driver out of staging
On 12/20/2017 12:42 PM, Greg KH wrote:
> 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?
Not sure i get your comment. Aren't we talking about the headers in there?
This was your original comment:
> Also, what's up with the .h files in drivers/staging/fsl-bus/include?
> You didn't touch those with this movement, right? Why?
---
Best Regards, Laurentiu
Powered by blists - more mailing lists