From: Ian Abbott <abbotti@mev.co.uk>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Amaury Denoyelle <amaury.denoyelle@gmail.com>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] Staging: comedi: fix line longer than 80 chars in cb_pcidas64.c
Date: Wed, 20 May 2015 10:00:45 +0100 [thread overview]
Message-ID: <555C4D3D.7040404@mev.co.uk> (raw)
In-Reply-To: <20150520082223.GB2997@sudip-PC>
On 20/05/15 09:22, Sudip Mukherjee wrote:
> On Wed, May 20, 2015 at 09:24:18AM +0200, Amaury Denoyelle wrote:
>> Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
>>
>>> On Tue, May 19, 2015 at 07:57:49PM +0200, Amaury Denoyelle wrote:
>>> <snip>
>>>> @@ -1381,7 +1382,9 @@ static int set_ai_fifo_segment_length(struct comedi_device *dev,
>>>> return devpriv->ai_fifo_segment_length;
>>>> }
>>>>
>>>> -/* adjusts the size of hardware fifo (which determines block size for dma xfers) */
>>>> +/*
>>>> + * adjusts the size of hardware fifo (which determines block size for dma xfers)
>>>> + */
>>> I did not understand this one. You are not breaking the comment into
>>> two lines, then why multiline style?
>>>
>>>> const struct pcidas64_board *thisboard = dev->board_ptr;
>>>> @@ -1588,7 +1591,9 @@ static inline void warn_external_queue(struct comedi_device *dev)
>>>> "Use internal AI channel queue (channels must be consecutive and use same range/aref)\n");
>>>> }
>>>>
>>>> -/* Their i2c requires a huge delay on setting clock or data high for some reason */
>>>> +/*
>>>> + * their i2c requires a huge delay on setting clock or data high for some reason
>>>> + */
>>> same here.
>>>
>>
>> The single-line version of these comments are over 80 characters (just
>> because of the "*/" characters), so I had to split them over several
>> lines.
> yes, i noticed. its almost 84 char. but after applying your patch also
> it comes to 81.
Really? I only see 80 characters.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2015-05-20 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 14:47 [PATCH 1/1] " Amaury Denoyelle
2015-05-18 4:37 ` Sudip Mukherjee
2015-05-18 17:56 ` [PATCH v2] " Amaury Denoyelle
2015-05-18 18:51 ` Amaury Denoyelle
2015-05-19 5:47 ` Sudip Mukherjee
2015-05-19 17:57 ` [PATCH v3 0/2] staging: comedi: fix coding style " Amaury Denoyelle
2015-05-19 17:57 ` [PATCH v3 1/2] Staging: comedi: fix line longer than 80 chars " Amaury Denoyelle
2015-05-20 5:02 ` Sudip Mukherjee
2015-05-20 7:24 ` Amaury Denoyelle
2015-05-20 8:22 ` Sudip Mukherjee
2015-05-20 9:00 ` Ian Abbott [this message]
2015-05-20 9:29 ` Sudip Mukherjee
2015-05-20 8:59 ` Ian Abbott
2015-05-19 17:57 ` [PATCH v3 2/2] Staging: comedi: fix style for multi-line comments " Amaury Denoyelle
2015-05-20 8:59 ` Ian Abbott
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=555C4D3D.7040404@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=amaury.denoyelle@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@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
Powered by JetHome