From: Masaru Nomura <massa.nomura@gmail.com>
To: gregkh@linuxfoundation.org, andreas.dilger@intel.com,
oleg.drokin@intel.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: [PATCH 0/5] staging: lustre: lnet: klnds: Fix coding style in socklnd.c
Date: Sun, 18 May 2014 18:19:12 +0100 [thread overview]
Message-ID: <1400433557-24985-1-git-send-email-massa.nomura@gmail.com> (raw)
These patches fix warnings below in socklnd.c to meet coding style.
Also fix some indenting due to changes to keep readability.
WARNING: space prohibited between function name and open parenthesis '('
WARNING: line over 80 characters
Masaru Nomura (5):
staging: lustre: lnet: socklnd: Remove prohibited space
staging: lustre: lnet: socklnd: Clean up memset(...)
staging: lustre: lnet: socklnd: Clean up CDEBUG(...)
staging: lustre: lnet: socklnd: Clean up ksocknal_get_peer_info(...)
staging: lustre: lnet: socklnd: Clean up ksocknal_create_conn(...)
.../staging/lustre/lnet/klnds/socklnd/socklnd.c | 242 ++++++++++----------
1 file changed, 121 insertions(+), 121 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-05-18 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 17:19 Masaru Nomura [this message]
2014-05-18 17:19 ` [PATCH 1/5] staging: lustre: lnet: socklnd: Remove prohibited space Masaru Nomura
2014-05-18 17:19 ` [PATCH 2/5] staging: lustre: lnet: socklnd: Clean up memset(...) Masaru Nomura
2014-05-18 17:27 ` Joe Perches
2014-05-18 19:12 ` Masaru Nomura
2014-05-20 8:50 ` walter harms
2014-05-18 17:19 ` [PATCH 3/5] staging: lustre: lnet: socklnd: Clean up CDEBUG(...) Masaru Nomura
2014-05-18 17:19 ` [PATCH 4/5] staging: lustre: lnet: socklnd: Clean up ksocknal_get_peer_info(...) Masaru Nomura
2014-05-18 17:19 ` [PATCH 5/5] staging: lustre: lnet: socklnd: Clean up ksocknal_create_conn(...) Masaru Nomura
2014-05-18 20:33 ` [PATCH 0/5] staging: lustre: lnet: klnds: Fix coding style in socklnd.c 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=1400433557-24985-1-git-send-email-massa.nomura@gmail.com \
--to=massa.nomura@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®