From: Joe Perches <joe@perches.com>
To: "Drokin, Oleg" <oleg.drokin@intel.com>,
Panos Vlachos <panosvlchs@gmail.com>
Cc: "<devel@driverdev.osuosl.org>" <devel@driverdev.osuosl.org>,
"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>,
"Dilger, Andreas" <andreas.dilger@intel.com>
Subject: Re: [PATCH 2/2] Staging: Lustre: Fixed coding style issues
Date: Mon, 18 Apr 2016 01:47:36 -0700 [thread overview]
Message-ID: <1460969256.19090.110.camel@perches.com> (raw)
In-Reply-To: <F2DFC001-0530-488C-902F-53B5D6ECC501@intel.com>
On Sun, 2016-04-17 at 21:35 +0000, Drokin, Oleg wrote:
> On Apr 17, 2016, at 10:11 AM, Panos Vlachos wrote:
> > Fixed one coding style issue in the
> > file router_proc.c (Lustre staging driver)
> Perhaps it's best to reference what the issue is.
> I.e. "Fix too long line in …"
> and then in the actual message add that you just split it?
[]
> > diff --git a/drivers/staging/lustre/lnet/lnet/router_proc.c b/drivers/staging/lustre/lnet/lnet/router_proc.c
[]
> > @@ -32,7 +32,8 @@
> > */
> > #define LNET_PROC_CPT_BITS (LNET_CPT_BITS + 1)
> > /* change version, 16 bits or 8 bits */
> > -#define LNET_PROC_VER_BITS max_t(size_t, min_t(size_t, LNET_LOFFT_BITS, 64) / 4, 8)
> > +#define LNET_PROC_VER_BITS \
> > +max_t(size_t, min_t(size_t, LNET_LOFFT_BITS, 64) / 4, 8)
> Hm, I am not sure this is an improvement, you might want to at least place a tab at the start of this
> second line, so that indentation helps us better see it's a continuation of the previous one.
Given:
#define LNET_LOFFT_BITS (sizeof(loff_t) * 8)
and:
include/linux/types.h:typedef __kernel_loff_t loff_t;
include/uapi/asm-generic/posix_types.h:typedef long long __kernel_loff_t;
and this isn't going to change any time soon,
maybe this #define isn't particularly useful and
#define LNET_PROC_VER_BITS 16
is sufficient.
prev parent reply other threads:[~2016-04-18 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 14:11 Panos Vlachos
2016-04-17 21:35 ` Drokin, Oleg
2016-04-18 8:47 ` Joe Perches [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=1460969256.19090.110.camel@perches.com \
--to=joe@perches.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=panosvlchs@gmail.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
all inboxes | Powered by JetHome®