[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1301181524110.1190-100000@iolanthe.rowland.org>
Date: Fri, 18 Jan 2013 15:29:23 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: David Miller <davem@...emloft.net>
cc: freddy@...x.com.tw, <netdev@...r.kernel.org>,
<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<louis@...x.com.tw>
Subject: Re: [PATCH, resubmit] ax88179_178a: ASIX AX88179_178A USB 3.0/2.0
to gigabit ethernet adapter driver
On Fri, 18 Jan 2013, David Miller wrote:
> > + ret = fn(dev, cmd, USB_DIR_IN | USB_TYPE_VENDOR |
> > + USB_RECIP_DEVICE, value, index, data, size);
>
> This is not indented properly. When a function call takes up
> multiple lines, the text on the second and subsequent lines must
> be left justified to the first column after the openning parenthesis
> of the function call, like this:
>
> function(arg1, arg2,
> arg3, arg4);
>
> You must use the appropriate combination of TAB and space characters
> to achieve this. If you are trying to only use TAB characters, you
> are doing it wrong.
Documentation/CodingStyle doesn't mention this. Does the networking
stack have its own special requirements, not listed in CodingStyle?
Alan Stern
P.S: The standard I have tried to follow for USB code is to indent
continuation lines by two tab stops more than the first line,
regardless of whether the break occurs inside a function call. I have
seen other people consistently indent continuation lines by 1/2 tab
stop (i.e., four spaces) beyond the first line.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists