From: Aastha Gupta <aastha.gupta4104@gmail.com>
To: outreachy-kernel@googlegroups.com,
Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Aastha Gupta <aastha.gupta4104@gmail.com>
Subject: [PATCH v2 0/8] staging: lustre: ldlm: fix line over 80 characters
Date: Fri, 15 Sep 2017 12:08:15 +0530 [thread overview]
Message-ID: <cover.1505456960.git.aastha.gupta4104@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1709150814460.2287@hadrien>
These patches fix checkpatch.pl warnings 'line over 80 characters' in ldlm files.
Changes in v2:
- edited commit messages to include the information about the file name
Aastha Gupta (8):
staging: lustre: ldlm: fix line over 80 characters in ldlm_extent
staging: lustre: ldlm: fix line over 80 characters in ldlm_flock
staging: lustre: ldlm: fix line over 80 characters in ldlm_internal
staging: lustre: ldlm: fix lines over 80 characters in ldlm_lock
staging: lustre: ldlm: fix lines over 80 characters in ldlm_lockd
staging: lustre: ldlm: fix lines over 80 characters in ldlm_pool
staging: lustre: ldlm: fix lines over 80 characters in ldlm_request
staging: lustre: ldlm: fix lines over 80 characters in ldlm_resource
drivers/staging/lustre/lustre/ldlm/ldlm_extent.c | 3 +-
drivers/staging/lustre/lustre/ldlm/ldlm_flock.c | 6 ++--
drivers/staging/lustre/lustre/ldlm/ldlm_internal.h | 4 ++-
drivers/staging/lustre/lustre/ldlm/ldlm_lock.c | 33 +++++++++++------
drivers/staging/lustre/lustre/ldlm/ldlm_lockd.c | 6 ++--
drivers/staging/lustre/lustre/ldlm/ldlm_pool.c | 6 ++--
drivers/staging/lustre/lustre/ldlm/ldlm_request.c | 41 ++++++++++++++--------
drivers/staging/lustre/lustre/ldlm/ldlm_resource.c | 3 +-
8 files changed, 67 insertions(+), 35 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2017-09-15 6:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 5:55 [PATCH 0/8] staging: lustre: ldlm: fix line over 80 characters Aastha Gupta
2017-09-15 5:55 ` [PATCH 1/8] " Aastha Gupta
2017-09-15 5:55 ` [PATCH 2/8] " Aastha Gupta
2017-09-15 5:55 ` [PATCH 3/8] " Aastha Gupta
2017-09-15 5:55 ` [PATCH 4/8] staging: lustre: ldlm: fix lines " Aastha Gupta
2017-09-15 5:55 ` [PATCH 5/8] " Aastha Gupta
2017-09-15 5:55 ` [PATCH 6/8] " Aastha Gupta
2017-09-15 5:55 ` [PATCH 7/8] " Aastha Gupta
2017-09-15 5:55 ` [PATCH 8/8] " Aastha Gupta
2017-09-15 6:16 ` [Outreachy kernel] [PATCH 0/8] staging: lustre: ldlm: fix line " Julia Lawall
2017-09-15 6:38 ` Aastha Gupta [this message]
2017-09-15 6:38 ` [PATCH v2 1/8] staging: lustre: ldlm: fix line over 80 characters in ldlm_extent Aastha Gupta
2017-09-15 6:38 ` [PATCH v2 2/8] staging: lustre: ldlm: fix line over 80 characters in ldlm_flock Aastha Gupta
2017-09-15 6:38 ` [PATCH v2 3/8] staging: lustre: ldlm: fix line over 80 characters in ldlm_internal Aastha Gupta
2017-09-15 6:38 ` [PATCH v2 4/8] staging: lustre: ldlm: fix lines over 80 characters in ldlm_lock Aastha Gupta
2017-09-15 6:38 ` [PATCH v2 5/8] staging: lustre: ldlm: fix lines over 80 characters in ldlm_lockd Aastha Gupta
2017-09-15 6:38 ` [PATCH v2 6/8] staging: lustre: ldlm: fix lines over 80 characters in ldlm_pool Aastha Gupta
2017-09-15 6:38 ` [PATCH v2 7/8] staging: lustre: ldlm: fix lines over 80 characters in ldlm_request Aastha Gupta
2017-09-15 6:38 ` [PATCH v2 8/8] staging: lustre: ldlm: fix lines over 80 characters in ldlm_resource Aastha Gupta
2017-09-15 7:29 ` [Outreachy kernel] [PATCH 0/8] staging: lustre: ldlm: fix line over 80 characters Dilger, Andreas
2017-09-15 7:57 ` [PATCH v3] staging: lustre: ldlm: fix lines over 80 characters in ldlm files Aastha Gupta
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=cover.1505456960.git.aastha.gupta4104@gmail.com \
--to=aastha.gupta4104@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=oleg.drokin@intel.com \
--cc=outreachy-kernel@googlegroups.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.