From: Johan Hovold <johan@kernel.org>
To: "Frank A. Cancio Bello" <frank@generalsoftwareinc.com>
Cc: pablo@netfilter.org, Julia.Lawall@lip6.fr,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 1/6] staging: greybus: Remove unnecessary blank lines
Date: Sat, 21 Oct 2017 12:09:38 +0200 [thread overview]
Message-ID: <20171021100938.GC1226@localhost> (raw)
In-Reply-To: <870ff7f2e00dcc63442173183383490a0adc3169.1508457306.git.frank@generalsoftwareinc.com>
On Thu, Oct 19, 2017 at 08:06:48PM -0400, Frank A. Cancio Bello wrote:
> Remove unnecessary blank lines to reduce file length and address
> checkpatch messages:
> CHECK: Please don't use multiple blank lines
> CHECK: Blank lines aren't necessary before a close brace '}'
>
> Signed-off-by: Frank A. Cancio Bello <frank@generalsoftwareinc.com>
> ---
> diff --git a/drivers/staging/greybus/connection.c b/drivers/staging/greybus/connection.c
> index 2cf6464..cb96877 100644
> --- a/drivers/staging/greybus/connection.c
> +++ b/drivers/staging/greybus/connection.c
> @@ -12,17 +12,13 @@
> #include "greybus.h"
> #include "greybus_trace.h"
>
> -
> #define GB_CONNECTION_CPORT_QUIESCE_TIMEOUT 1000
>
> -
> static void gb_connection_kref_release(struct kref *kref);
>
> -
> static DEFINE_SPINLOCK(gb_connections_lock);
> static DEFINE_MUTEX(gb_connection_mutex);
>
> -
Here double newlines are used to separate and group defines, function
prototypes, and static variables, which is perfectly fine.
Johan
next prev parent reply other threads:[~2017-10-21 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 0:06 [PATCH 0/6] staging: greybus: Correct code style issues Frank A. Cancio Bello
2017-10-20 0:06 ` [PATCH 1/6] staging: greybus: Remove unnecessary blank lines Frank A. Cancio Bello
2017-10-21 10:09 ` Johan Hovold [this message]
2017-10-20 0:22 ` [PATCH 2/6] staging: greybus: Fix alignment issues Frank A. Cancio Bello
2017-10-20 0:22 ` [PATCH 3/6] staging: greybus: Use u32 instead of uint32_t Frank A. Cancio Bello
2017-10-20 0:23 ` [PATCH 4/6] staging: greybus: Add space around ternary operator Frank A. Cancio Bello
2017-10-20 0:24 ` [PATCH 5/6] staging: greybus: Move logical operator in previous line Frank A. Cancio Bello
2017-10-20 0:26 ` [PATCH 6/6] staging: greybus: Rewrite NULL comparisons Frank A. Cancio Bello
2017-10-21 10:07 ` [PATCH 0/6] staging: greybus: Correct code style issues Johan Hovold
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=20171021100938.GC1226@localhost \
--to=johan@kernel.org \
--cc=Julia.Lawall@lip6.fr \
--cc=elder@kernel.org \
--cc=frank@generalsoftwareinc.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=pablo@netfilter.org \
/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.