Re: newbies CheckpatchTips for multiline statements (Breaking function calls)

2014-12-27 Thread Anand Moon
Hi All, If we are using the correct plugin in vim. We could hardly face this situation indent of the Linux kernel code. Below link helps http://www.vim.org/scripts/script.php?script_id=4369 -Anand Moon On Wednesday, December 17, 2014 4:25 PM, Bjørn Mork wrote: Joe Perches writes: >

Re: newbies CheckpatchTips for multiline statements (Breaking function calls)

2014-12-17 Thread Bjørn Mork
Joe Perches writes: > This style is fine, and generally perferred. However, some driver > writers prefer to have the trailing line of a function call line up with > the starting '('. They use tabs, followed by spaces, to align the > trailing line: > > > pdata->urbdata = usb_alloc_coher

Re: newbies CheckpatchTips for multiline statements (Breaking function calls)

2014-12-16 Thread Mandeep Sandhu
> > btw: there's a perferred/preferred tyop too. > Sorry, but I just couldn't ignore the irony of this. :P -mandeep ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

newbies CheckpatchTips for multiline statements (Breaking function calls)

2014-12-16 Thread Joe Perches
http://kernelnewbies.org/CheckpatchTips The block about "Breaking function calls" is dubious. The majority of code today uses arguments aligned to parenthesis. The suggested 1 tab is in fact very infrequently used. CodingStyle has this as "substantially to the right", not 1 tab. btw: there's a