From: "Drokin, Oleg" <oleg.drokin@intel.com>
To: Anil Belur <askb23@gmail.com>
Cc: "Dilger, Andreas" <andreas.dilger@intel.com>,
"<gregkh@linuxfoundation.org>" <gregkh@linuxfoundation.org>,
"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>,
"<hpdd-discuss@lists.01.org>" <hpdd-discuss@ml01.01.org>
Subject: Re: [PATCH v4 7/8] staging: lustre: lclient: lcommon_cl.c fixing coding style issues
Date: Mon, 16 Jun 2014 14:17:56 +0000 [thread overview]
Message-ID: <33547832-F895-4D4E-AB26-A4D4B11681B7@intel.com> (raw)
In-Reply-To: <1402917203-12798-8-git-send-email-askb23@gmail.com>
On Jun 16, 2014, at 7:13 AM, Anil Belur wrote:
> From: Anil Belur <askb23@gmail.com>
>
> fixed: WARNING: line over 80 characters, used a new variable 'check' to
> store the offset. Replace "unsigned long" with "u64" type fir
> '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 c180a20..440d7c2 100644
> --- a/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
> +++ b/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
> @@ -864,10 +864,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;
> + u64 cur_index = start >> PAGE_CACHE_SHIFT;
Well, size is of type loff_t, so I imagine it's most natural to make cur_index to be loff_t too,
just like what you do with the newly added check (not very great name, btw, size_index?) variable
Bye,
Oleg
next prev parent reply other threads:[~2014-06-16 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 11:13 [PATCH v4] staging: lustre: lclient: " Anil Belur
2014-06-16 11:13 ` [PATCH v4 1/8] staging: lustre: lclient: glimpse.c " Anil Belur
2014-06-16 11:13 ` [PATCH v4 2/8] " Anil Belur
2014-06-16 11:13 ` [PATCH v4 3/8] staging: lustre: lclient: lcommon_misc.c " Anil Belur
2014-06-16 11:13 ` [PATCH v4 4/8] staging: lustre: lclient: lcommon_cl.c " Anil Belur
2014-06-16 11:13 ` [PATCH v4 5/8] " Anil Belur
2014-06-16 11:13 ` [PATCH v4 6/8] " Anil Belur
2014-06-16 11:13 ` [PATCH v4 7/8] " Anil Belur
2014-06-16 14:17 ` Drokin, Oleg [this message]
2014-06-16 11:13 ` [PATCH v4 8/8] " Anil Belur
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=33547832-F895-4D4E-AB26-A4D4B11681B7@intel.com \
--to=oleg.drokin@intel.com \
--cc=andreas.dilger@intel.com \
--cc=askb23@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpdd-discuss@ml01.01.org \
--cc=linux-kernel@vger.kernel.org \
/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®