[lustre-devel] Working on client merge

Chris Hanna hannac at iu.edu
Wed Jun 10 11:11:15 PDT 2015


I'd be happy to continue work on the format, whitespace, and coding
style changes, on any areas that aren't already spoken for. 

Chris

On 6/10/15 1:59 PM, Patrick Farrell wrote:
> I suggest breaking it up first by work type.  As Julia noted,
> coccinelle/checkpatch/etc fixes (coding style, straightforward errors
> caught by the tools, sparse complaints, warnings, etc.) rarely require
> awareness of the larger flow of the design.
>
> Then there is some other types of cleanup that require more Lustre
> knowledge to tackle.  If possible, those would be better for someone
> like Ben (or you, James) to work on.  What do we have for that kind of
> work?
>
> - Patrick
>
> On 06/10/2015 12:16 PM, Julia Lawall wrote:
>>
>> On Wed, 10 Jun 2015, Simmons, James A. wrote:
>>
>>>> Where would be a good place to get started with helping merge the
>>>> client
>>> into mainline?
>>>
>>>  
>>> Hi Ben
>>>
>>>  
>>>       Thanks for helping out for this work. I added people in the
>>> chain that
>>> have contributed a great
>>>
>>> deal to the upstream client so we can coordinate our work. Also I
>>> like to
>>> make people aware
>>>
>>> a lustre IRC channel does exist.   Andreas can supply the details
>>> about the
>>> IRC channel. Currently
>>>
>>> my work has been focused on the libcfs/lnet layer. I had discuss
>>> early with
>>> Mike Shuey  since he
>>>
>>> was also working in that area but will be migrating to the lustre core.
>>>
>>>  
>>>      Since more people are getting involved we need to find  a way
>>> to break
>>> up the work to avoid
>>>
>>> duplicate work. Should the work be broken  up by layer, i.e lov,
>>> mdc, or by
>>> task such as removing
>>>
>>> specific checkpatch errors with files?
>> For the work I have done with Coccinelle, it is more convenient to do
>> the
>> whole thing.  Breaking things up by layer is not helpful.
>>
>> This is just a data point, though. It doesn't have to imply anything
>> about
>> how others work on the code.
>>
>> julia
>>
>>
>> _______________________________________________
>> lustre-devel mailing list
>> lustre-devel at lists.lustre.org
>> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>
>
>
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20150610/3241ab71/attachment-0001.htm>


More information about the lustre-devel mailing list