From: "Dilger, Andreas" <andreas.dilger@intel.com>
To: Anil Belur <askb23@gmail.com>,
"Drokin, Oleg" <oleg.drokin@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpdd-discuss@lists.01.org" <hpdd-discuss@ml01.01.org>
Subject: Re: [PATCH v6 8/8] staging: lustre: lclient: lcommon_cl.c fixing coding style issues
Date: Tue, 17 Jun 2014 16:25:14 +0000 [thread overview]
Message-ID: <CFC5C7D5.ABDC7%andreas.dilger@intel.com> (raw)
In-Reply-To: <1402983839-3549-9-git-send-email-askb23@gmail.com>
On 2014/06/16, 11:43 PM, "Anil Belur" <askb23@gmail.com> wrote:
>From: Anil Belur <askb23@gmail.com>
>
>fixed: WARNING: suspect code indent for conditional statements (32, 32)
>Signed-off-by: Anil Belur <askb23@gmail.com>
>---
> drivers/staging/lustre/lustre/lclient/lcommon_cl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
>b/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
>index e2da397..3b2b995 100644
>--- a/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
>+++ b/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
>@@ -825,8 +825,8 @@ int ccc_prep_size(const struct lu_env *env, struct
>cl_object *obj,
> loff_t size_index = ((size - 1) >> PAGE_CACHE_SHIFT);
>
> if ((size == 0 && cur_index != 0) ||
>- (size_index < cur_index))
>- *exceed = 1;
>+ (size_index < cur_index))
The old indentation of this line (aligned after '(' on the previous line)
was better. Note also that there is no need for parenthesis around this
statement.
>+ *exceed = 1;
> }
> return result;
> } else {
>--
>1.9.0
>
>
Cheers, Andreas
--
Andreas Dilger
Lustre Software Architect
Intel High Performance Data Division
prev parent reply other threads:[~2014-06-17 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 5:43 [PATCH v6] staging: lustre: lclient: fixing coding style issues Anil Belur
2014-06-17 5:43 ` [PATCH v6 1/8] staging: lustre: lclient: glimpse.c " Anil Belur
2014-06-17 5:43 ` [PATCH v6 2/8] " Anil Belur
2014-06-17 5:43 ` [PATCH v6 3/8] staging: lustre: lclient: lcommon_misc.c " Anil Belur
2014-06-17 16:15 ` Dilger, Andreas
2014-06-18 2:54 ` Anil Shashikumar Belur
2014-06-17 5:43 ` [PATCH v6 4/8] staging: lustre: lclient: lcommon_cl.c " Anil Belur
2014-06-17 5:43 ` [PATCH v6 5/8] " Anil Belur
2014-06-17 5:43 ` [PATCH v6 6/8] " Anil Belur
2014-06-17 5:43 ` [PATCH v6 7/8] " Anil Belur
2014-06-17 16:23 ` Dilger, Andreas
2014-06-18 2:54 ` Anil Shashikumar Belur
2014-06-17 5:43 ` [PATCH v6 8/8] " Anil Belur
2014-06-17 16:25 ` Dilger, Andreas [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=CFC5C7D5.ABDC7%andreas.dilger@intel.com \
--to=andreas.dilger@intel.com \
--cc=askb23@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpdd-discuss@ml01.01.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