From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752007AbcAERDq (ORCPT ); Tue, 5 Jan 2016 12:03:46 -0500 Received: from mail-vk0-f67.google.com ([209.85.213.67]:34242 "EHLO mail-vk0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751863AbcAERDo (ORCPT ); Tue, 5 Jan 2016 12:03:44 -0500 MIME-Version: 1.0 In-Reply-To: References: <1452010258.4334.139.camel@perches.com> Date: Tue, 5 Jan 2016 14:03:43 -0300 Message-ID: Subject: Re: [PATCH 09/17] usb: host: ehci-dbg: fix up function definitions From: "Geyslan G. Bem" To: Alan Stern Cc: Joe Perches , LKML , Greg Kroah-Hartman , linux-usb@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2016-01-05 13:29 GMT-03:00 Alan Stern : > On Tue, 5 Jan 2016, Joe Perches wrote: > >> On Tue, 2016-01-05 at 11:06 -0500, Alan Stern wrote: >> > Trying to come up with hard-and-fast rules for this sort of thing is >> > pretty hopeless. Even "Maximize readability" doesn't work too well, >> > because different people find different things most readable. >> >> Readability is mostly habituation. > > Indeed. Ditto. > >> Align to open parenthesis is relatively easy to implement, >> but it can get out of hand too with long naming. It's easy and it's consistent (the place of sequential lines). > > That's why I dislike it. Plus the fact that it results in > continuations of different lines being indented by different amounts. The different amounts is the price to pay for that indentation, but it will mostly make the style consistent and easy as Joe stated. I'm not claiming for that changing, just debating. :-D But IMHO standardization could make things easier. > > Alan Stern > -- Regards, Geyslan G. Bem hackingbits.com