[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120709.141714.1072959067688919521.davem@davemloft.net>
Date: Mon, 09 Jul 2012 14:17:14 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: B04825@...escale.com
Cc: afleming@...escale.com, netdev@...r.kernel.org
Subject: Re: [PATCH] net/fsl_pq_mdio: use spin_event_timeout() to poll the
indicator register
From: Tabi Timur-B04825 <B04825@...escale.com>
Date: Mon, 9 Jul 2012 14:31:33 +0000
> David Miller wrote:
>
>> Define a macro for the timeout value rather than use an arbitrary
>> constant.
>
> Ok.
>
>>> + status = spin_event_timeout(!(in_be32(®s->miimind) & MIIMIND_BUSY),
>>> + 1000, 0);
>>
>> This indentation is absolutely terrible.
>
> Can you give me a clue as to how you think it should look? I could not
> come up with a good way to break up these lines and keep them under 80
> characters.
It's not the length of the first line, it's how the second line was
indented.
Always line up the arguments on the second and subsequent lines right
after the column containing the openning "(" on the first line.
foo = function(arg1,
arg2);
Do you really mean that:
foo = function(arg1,
arg2);
doesn't look like complete and utter shit to you?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists