From: Greg KH <greg@kroah.com>
To: Balavasu <kp.balavasu@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andreas.dilger@intel.com, oleg.drokin@intel.com
Subject: Re: [PATCH 2/2] staging: lustre: lnet: lnet: trailing statements should be on next line
Date: Fri, 31 Oct 2014 13:50:36 -0700 [thread overview]
Message-ID: <20141031205036.GC20417@kroah.com> (raw)
In-Reply-To: <20141031182040.GA7916@vasu-Inspiron-3542>
On Fri, Oct 31, 2014 at 11:50:40PM +0530, Balavasu wrote:
> This patch fixes the checkpatch.pl issue
> Error: trailing statements should be on next line
>
> Signed-off-by: Balavasu <kp.balavasu@gmail.com>
> ---
> drivers/staging/lustre/lnet/lnet/router.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Same comments as 1/2
next prev parent reply other threads:[~2014-10-31 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 18:20 [PATCH 2/2] staging: lustre: lnet: lnet: trailing statements should be on next line Balavasu
2014-10-31 20:50 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-23 18:51 Balavasu
2014-11-24 6:07 Balavasu kuppusammyprathaban
2015-01-15 5:42 Balavasu
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=20141031205036.GC20417@kroah.com \
--to=greg@kroah.com \
--cc=andreas.dilger@intel.com \
--cc=kp.balavasu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg.drokin@intel.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.