linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Sedat Dilek <sedat.dilek@gmail.com>,
	Oscar Forner Martinez <oscar.forner.martinez@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bcma: fix three coding style issues, more than 80 characters per line
Date: Sun, 28 Dec 2014 16:01:08 +0100	[thread overview]
Message-ID: <54A01B34.4000002@broadcom.com> (raw)
In-Reply-To: <CACna6rwRPwannK7TviY7AmhMvd09h-zLXJOBEK-U09dz=5ezKQ@mail.gmail.com>

On 12/28/14 15:02, Rafał Miłecki wrote:
> On 28 December 2014 at 10:12, Sedat Dilek<sedat.dilek@gmail.com>  wrote:
>> On Sun, Dec 28, 2014 at 9:53 AM, Rafał Miłecki<zajec5@gmail.com>  wrote:
>>> On 28 December 2014 at 06:50, Sedat Dilek<sedat.dilek@gmail.com>  wrote:
>>>> On Sun, Dec 28, 2014 at 12:44 AM, Rafał Miłecki<zajec5@gmail.com>  wrote:
>>>>> On 27 December 2014 at 20:24, Oscar Forner Martinez
>>>>> <oscar.forner.martinez@gmail.com>  wrote:
>>>>>> Three lines with more than 80 characters per line have been split in several lines.
>>>>>>
>>>>>> Signed-off-by: Oscar Forner Martinez<oscar.forner.martinez@gmail.com>
>>>>>
>>>>> Acked-by: Rafał Miłecki<zajec5@gmail.com>
>>>>>
>>>>
>>>> As for the comment-line changes... 80+ chars are allowed for better readability.
>>>> So, please don't do that.
>>>> [ Checkpatch should not warn on this especially for comments. ]
>>>
>>> We almost always split long comments into separated lines in the
>>> kernel. What's different with this case?
>>>
>>
>> 1st it is not mandatory.
>>
>> 2nd it is more readable in one line.
>>
>> -                       /* 4706 CC and PMU watchdogs are clocked at
>> 1/4 of ALP clock */
>> +                       /* 4706 CC and PMU watchdogs are clocked at 1/4 of ALP
>> +                        * clock
>> +                        */
>>
>> I agree with you when the comment would be longer.
>
> So I guess there is some rule like
> "Don't use 2 lines if there is 80 chars + one word"
> ? Where can I find such rules?

Personally, I don't like taking this sliding slope. Just stick to the 80 
characters rule and add a few words in the comment, eg:

			/* The BCM4706 ChipCommon and PMU watchdogs are
			 * clocked at one quarter of the ALP clock.
			 */

Regards,
Arend


  reply	other threads:[~2014-12-28 15:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-27 19:24 [PATCH] bcma: fix three coding style issues, more than 80 characters per line Oscar Forner Martinez
2014-12-27 20:19 ` Rafał Miłecki
     [not found]   ` <CADZ0Xg++nexnzmuaOp+MHXBbODwSpoEYNcbDU=X9tNYbzh=W-w@mail.gmail.com>
     [not found]     ` <CADZ0XgJ=LU3n55MxcHUMdX7uRcOm-m+=DFLGDi6PPkj+5=y1sg@mail.gmail.com>
2014-12-27 23:42       ` Rafał Miłecki
2014-12-27 23:44 ` Rafał Miłecki
2014-12-28  5:50   ` Sedat Dilek
2014-12-28  8:53     ` Rafał Miłecki
2014-12-28  9:12       ` Sedat Dilek
2014-12-28 14:02         ` Rafał Miłecki
2014-12-28 15:01           ` Arend van Spriel [this message]
2014-12-29  7:16   ` Kalle Valo
2015-01-07 11:18     ` Òscar Forner Martínez
2015-01-07 13:57       ` Kalle Valo
2015-01-07 14:01         ` Òscar Forner Martínez
2015-01-15 12:42 ` Kalle Valo

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=54A01B34.4000002@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=oscar.forner.martinez@gmail.com \
    --cc=sedat.dilek@gmail.com \
    --cc=zajec5@gmail.com \
    /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).