linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakshi Vaid <sakshivaid95@gmail.com>
To: andreas.dilger@intel.com
Cc: gregkh@linuxfoundation.org, jinshan.xiong@intel.com,
	HPDD-discuss@ml01.01.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org,
	Sakshi Vaid <sakshivaid95@gmail.com>
Subject: [PATCH v2] Staging: lustre: lustre: lov: lov_dev.c: Added missing blank line
Date: Mon, 14 Sep 2015 20:59:24 +0530	[thread overview]
Message-ID: <1442244564-3284-1-git-send-email-sakshivaid95@gmail.com> (raw)
In-Reply-To: <1442221884-5346-1-git-send-email-sakshivaid95@gmail.com>

line 158: WARNING: Missing a blank line after declarations
line 183: WARNING: Missing a blank line after declarations

Added a missing blank line after declartions.

Signed-off-by: Sakshi Vaid <sakshivaid95@gmail.com>
---
 drivers/staging/lustre/lustre/lov/lov_dev.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/staging/lustre/lustre/lov/lov_dev.c b/drivers/staging/lustre/lustre/lov/lov_dev.c
index 796a015..aadb8f2 100644
--- a/drivers/staging/lustre/lustre/lov/lov_dev.c
+++ b/drivers/staging/lustre/lustre/lov/lov_dev.c
@@ -155,6 +155,7 @@ static void lov_key_fini(const struct lu_context *ctx,
 			 struct lu_context_key *key, void *data)
 {
 	struct lov_thread_info *info = data;
+
 	LINVRNT(list_empty(&info->lti_closure.clc_list));
 	OBD_SLAB_FREE_PTR(info, lov_thread_kmem);
 }
@@ -180,6 +181,7 @@ static void lov_session_key_fini(const struct lu_context *ctx,
 				 struct lu_context_key *key, void *data)
 {
 	struct lov_session *info = data;
+
 	OBD_SLAB_FREE_PTR(info, lov_session_kmem);
 }
 
-- 
1.9.1


      parent reply	other threads:[~2015-09-14 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14  9:11 [PATCH] Staging: lustre: lustre: lov: lov_dev.c: Added missing blank line Sakshi Vaid
2015-09-14 14:12 ` Greg KH
2015-09-14 15:29 ` Sakshi Vaid [this message]

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=1442244564-3284-1-git-send-email-sakshivaid95@gmail.com \
    --to=sakshivaid95@gmail.com \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jinshan.xiong@intel.com \
    --cc=linux-kernel@vger.kernel.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 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).