netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: freddy@asix.com.tw
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, louis@asix.com.tw
Subject: Re: [PATCH, resubmit] ax88179_178a: ASIX AX88179_178A USB 3.0/2.0 to gigabit ethernet adapter driver
Date: Fri, 18 Jan 2013 14:23:16 -0500 (EST)	[thread overview]
Message-ID: <20130118.142316.708739494707619536.davem@davemloft.net> (raw)
In-Reply-To: <1358415174-4348-1-git-send-email-freddy@asix.com.tw>

From: Freddy Xin <freddy@asix.com.tw>
Date: Thu, 17 Jan 2013 17:32:54 +0800

> +struct ax88179_rx_pkt_header {
> +
> +	u8	l4_csum_err:1,

Get rid of such extraneous empty lines.  They do not add clarity,
rather they just take up space.

> +	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.

This code has a lot of other similar coding style errors, please
put some effort into fixing them up before you consider resubmitting
this driver.

All of the coding style errors are probably why nobody reviewed your
driver the first time around, there's already enough properly styled
submissions to review.

  reply	other threads:[~2013-01-18 19:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17  9:32 [PATCH, resubmit] ax88179_178a: ASIX AX88179_178A USB 3.0/2.0 to gigabit ethernet adapter driver Freddy Xin
2013-01-18 19:23 ` David Miller [this message]
2013-01-18 20:29   ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2013-01-23  2:32 Freddy Xin
2013-01-23  4:15 ` David Miller
2013-01-26 23:13 ` Michael Leun
2013-01-28  9:07   ` Bjørn Mork
2013-01-28 13:36     ` Freddy
2013-01-28 14:24       ` Bjørn Mork
2013-01-28 16:42       ` Michael Leun
2013-02-07  4:36 Freddy Xin
2013-02-07  5:45 ` Stephen Hemminger
     [not found] ` <1360211794-4737-1-git-send-email-freddy-knRN6Y/kmf1NUHwG+Fw1Kw@public.gmane.org>
2013-02-07  5:46   ` Stephen Hemminger
2013-02-07  6:50     ` Freddy
2013-02-07 13:39 Freddy Xin
2013-02-07 20:02 ` Ben Hutchings
2013-02-07 20:05   ` David Miller
2013-02-08  3:41   ` Freddy
2013-02-08 10:23   ` David Laight
2013-02-08 19:23     ` David Miller
2013-02-27 12:01 [PATCH " Freddy Xin
2013-03-01 21:15 ` David Miller
2013-03-02 10:41 Freddy Xin
2013-03-03  6:44 ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130118.142316.708739494707619536.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=freddy@asix.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=louis@asix.com.tw \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).