From: "Drokin, Oleg" <oleg.drokin@intel.com>
To: 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: Sun, 17 Apr 2016 21:35:35 +0000 [thread overview]
Message-ID: <F2DFC001-0530-488C-902F-53B5D6ECC501@intel.com> (raw)
In-Reply-To: <1460902313-5327-1-git-send-email-panosvlchs@gmail.com>
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?
>
> Signed-off-by: Panos Vlachos <panosvlchs@gmail.com>
> ---
> drivers/staging/lustre/lnet/lnet/router_proc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/lustre/lnet/lnet/router_proc.c b/drivers/staging/lustre/lnet/lnet/router_proc.c
> index 65f65a3..87afb40 100644
> --- 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.
Thanks.
>
> #define LNET_PROC_HASH_BITS LNET_PEER_HASH_BITS
> /*
> --
> 1.9.1
>
next prev parent reply other threads:[~2016-04-17 21:35 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 [this message]
2016-04-18 8:47 ` Joe Perches
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=F2DFC001-0530-488C-902F-53B5D6ECC501@intel.com \
--to=oleg.drokin@intel.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--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®