On Aug 9, 2014, at 11:47 AM, Greg Kroah-Hartman wrote:
> On Sat, Aug 09, 2014 at 10:34:36AM -0400, Oleg Drokin wrote:
>>
>>> Because maybe these stats preceed the introduction of perf and other
>>> tracing/debug tools? I don't know, it's really low down on the list of
>>> reasons why lustre can't be merged out of staging at the moment, you all
>>> have much bigger issues to address first.
>>
>> I wonder what is the prioritized list you have in mind?
>
> Do I really have to spell out what is wrong with that codebase that
> needs to be fixed up? It took me 50+ patches for 3.17-rc1 to just fix
> up a _portion_ of the include file mess that is in there. Now is the
> first time the code actually _builds_ properly in the kernel tree (i.e.
> no magic header file include path modifications in Makefiles preventing
> individual files from being built correctly.)
Well, last time we discussed this topic, you said that moving most of lustre proc files
into sysfs and other suitable venues is what prevents moving lustre out of the
staging tree under fs/
There well might be include mess, but this is the first time I hear about it, and I have not seen
any build breakage or other obviously broken behavior.
I am sure there are more things too, that's why I am asking.
We are trying to deal with stuff we know about, but it's a bit harder to deal with the stuff we don't know about
that does not manifest itself in some clear way.
Bye,
Oleg
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
