From: Joe Perches <joe@perches.com>
To: Martin <martin.alonso@zoho.com>, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: skein: Remove extra blank lines
Date: Mon, 26 Sep 2016 09:26:12 -0700 [thread overview]
Message-ID: <1474907172.2238.15.camel@perches.com> (raw)
In-Reply-To: <1474901787-11881-1-git-send-email-martin.alonso@zoho.com>
On Mon, 2016-09-26 at 11:56 -0300, Martin wrote:
> Fix coding style issue "multiple blank lines"
> detected by checkpatch.pl in threefish_block.c file.
This has been submitted and rejected a couple times already.
The extra blank lines are to separate blocks.
Whatever the blocks are, perhaps _adding_ a comment line
for each block might be better than removing a blank line.
>
next prev parent reply other threads:[~2016-09-26 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 14:56 [PATCH] staging: skein: Remove extra blank lines Martin
2016-09-26 16:26 ` Joe Perches [this message]
2016-09-26 17:06 ` Martin Alonso
2016-09-27 7:18 ` Dan Carpenter
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=1474907172.2238.15.camel@perches.com \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.alonso@zoho.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