All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhanusree <bhanusreemahesh@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: outreachy-kernel@googlegroups.com, abbotti@mev.co.uk,
	gregkh@linuxfoundation.org, hsweeten@visionengravers.com
Subject: Re: [Outreachy kernel] [Outreachy Kernel][PATCH v5] staging:comedi:comedi_pci.h Prefer a maximum 75 chars per line
Date: Sun, 7 Oct 2018 00:43:16 +0530	[thread overview]
Message-ID: <6efbf8f0-a008-1b78-9a2e-e90af0f7e0ff@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1810062105410.2402@hadrien>



On Sunday 07 October 2018 12:36 AM, Julia Lawall wrote:
>
> On Sun, 7 Oct 2018, Bhanusree Pola wrote:
>
>> Adjust all lines exceeding 75 chars per line to fix checkpatch warning.
>>
>> Signed-off-by: Bhanusree Pola <bhanusreemahesh@gmail.com>
>> ---
>>
>> changes in v5:
>> -Fixed Change log
>> -Change in subject line.Do not send as 'Re:'
> It doesn't matter here, because this text will go away, but please get in
> the habit of putting at least one space after punctuation.  That is:
>
> Change in subject line. Do not send as 'Re:'
>
> Then things don't run together, and it is easier to read.
It is taking time for me to understand. Sometimes I'm doing it in haste. 
Thank you for making me understand.


  reply	other threads:[~2018-10-06 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 19:02 [Outreachy Kernel][PATCH v5] staging:comedi:comedi_pci.h Prefer a maximum 75 chars per line Bhanusree Pola
2018-10-06 19:06 ` [Outreachy kernel] " Julia Lawall
2018-10-06 19:13   ` Bhanusree [this message]
2018-10-06 19:31 ` Himanshu Jha
2018-10-06 19:41   ` Julia Lawall

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=6efbf8f0-a008-1b78-9a2e-e90af0f7e0ff@gmail.com \
    --to=bhanusreemahesh@gmail.com \
    --cc=abbotti@mev.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --cc=julia.lawall@lip6.fr \
    --cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.