public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 7/8] staging: lustre: lclient: lcommon_cl.c fixing coding style issues
Date: Tue, 17 Jun 2014 16:23:01 +0000	[thread overview]
Message-ID: <CFC5C64E.ABDAF%andreas.dilger@intel.com> (raw)
In-Reply-To: <1402983839-3549-8-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: line over 80 characters, used a new variable 'size_index'
>to
>store the offset. Replaceed "unsigned long" with  "loff_t" type for
>'cur_index'
>
>Signed-off-by: Anil Belur <askb23@gmail.com>
>---
> drivers/staging/lustre/lustre/lclient/lcommon_cl.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
>b/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
>index 2f51b76..e2da397 100644
>--- a/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
>+++ b/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
>@@ -821,10 +821,11 @@ int ccc_prep_size(const struct lu_env *env, struct
>cl_object *obj,
> 				 * linux-2.6.18-128.1.1 miss to do that.
> 				 * --bug 17336 */
> 				loff_t size = cl_isize_read(inode);
>-				unsigned long cur_index = start >> PAGE_CACHE_SHIFT;
>+				loff_t cur_index = start >> PAGE_CACHE_SHIFT;
>+				loff_t size_index = ((size - 1) >> PAGE_CACHE_SHIFT);

Should be an empty line between variable declarations and code.

> 
> 				if ((size == 0 && cur_index != 0) ||
>-				    (((size - 1) >> PAGE_CACHE_SHIFT) < cur_index))
>+				    (size_index < cur_index))
> 				*exceed = 1;
> 			}
> 			return result;
>-- 
>1.9.0
>
>


Cheers, Andreas
-- 
Andreas Dilger

Lustre Software Architect
Intel High Performance Data Division



  reply	other threads:[~2014-06-17 16:24 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 [this message]
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

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=CFC5C64E.ABDAF%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