From: Anil Shashikumar Belur <askb23@gmail.com>
To: "Drokin, Oleg" <oleg.drokin@intel.com>
Cc: "Dilger, Andreas" <andreas.dilger@intel.com>,
"<tao.peng@emc.com>" <tao.peng@emc.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 v5 7/8] staging: lustre: lclient: lcommon_cl.c fixing coding style issues
Date: Tue, 17 Jun 2014 10:26:17 +0530 [thread overview]
Message-ID: <539FCA71.2000702@gmail.com> (raw)
In-Reply-To: <6FD758BB-2803-41BC-BFBF-2A607A68EAFA@intel.com>
On Tuesday 17 June 2014 07:38 AM, Drokin, Oleg wrote:
> On Jun 16, 2014, at 12:22 PM, Anil Belur wrote:
>
>> From: Anil Belur <askb23@gmail.com>
>>
>> fixed: WARNING: line over 80 characters, used a new variable 'size_index' to
>> store the offset. Replace "unsigned long" with "u64" type for
> Apparently you forgot to update the comment.
Thanks Oleg - overlooked it, will fix this shortly.
next prev parent reply other threads:[~2014-06-17 4:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 16:22 [PATCH v5] staging: lustre: lclient: fixing coding style issues Anil Belur
2014-06-16 16:22 ` [PATCH v5 1/8] staging: lustre: lclient: glimpse.c " Anil Belur
2014-06-16 16:22 ` [PATCH v5 2/8] " Anil Belur
2014-06-16 16:22 ` [PATCH v5 3/8] staging: lustre: lclient: lcommon_misc.c " Anil Belur
2014-06-16 16:22 ` [PATCH v5 4/8] staging: lustre: lclient: lcommon_cl.c " Anil Belur
2014-06-16 16:22 ` [PATCH v5 5/8] " Anil Belur
2014-06-16 16:22 ` [PATCH v5 6/8] " Anil Belur
2014-06-16 16:22 ` [PATCH v5 7/8] " Anil Belur
2014-06-17 2:08 ` Drokin, Oleg
2014-06-17 4:56 ` Anil Shashikumar Belur [this message]
2014-06-16 16:22 ` [PATCH v5 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=539FCA71.2000702@gmail.com \
--to=askb23@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpdd-discuss@ml01.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=tao.peng@emc.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.