From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Vatika Harlalka <vatikaharlalka@gmail.com>,
outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v3] Staging: i2o: Remove space after the * in a pointer type variable.
Date: Wed, 18 Feb 2015 17:04:49 +0530 [thread overview]
Message-ID: <54E478D9.7070303@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150218111524.GA11738@gmail.com>
Hi Vatika,
On 02/18/2015 04:45 PM, Vatika Harlalka wrote:
> This patch is to remove space after the * in a pointer type variable declaration to follow kernel coding conventions.
You may have noticed that a limit of 80 characters is imposed in the
kernel coding style. It would be good to follow the same in the
changelog as well. So the patch looks is uniformly aligned throughout.
>
> Signed-off-by: Vatika Harlalka <vatikaharlalka@gmail.com>
> ---
>
> Changes in v3: Moved changelog below to "---" line.
> Changes in v2: Changed subject line to make it more descriptive.
>
> drivers/staging/i2o/debug.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/i2o/debug.c b/drivers/staging/i2o/debug.c
> index 7a16114..4f23e3f 100644
> --- a/drivers/staging/i2o/debug.c
> +++ b/drivers/staging/i2o/debug.c
> @@ -5,7 +5,7 @@
>
> static void i2o_report_util_cmd(u8 cmd);
> static void i2o_report_exec_cmd(u8 cmd);
> -static void i2o_report_fail_status(u8 req_status, u32 * msg);
> +static void i2o_report_fail_status(u8 req_status, u32 *msg);
I see that the definition of this function suffers from the same issue
down below in the file. You may want to correct that as well and club
both the changes in one patch.
> static void i2o_report_common_status(u8 req_status);
> static void i2o_report_common_dsc(u16 detailed_status);
>
Regards
Preeti U Murthy
prev parent reply other threads:[~2015-02-18 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 11:15 [PATCH v3] Staging: i2o: Remove space after the * in a pointer type variable Vatika Harlalka
2015-02-18 11:34 ` Preeti U Murthy [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=54E478D9.7070303@linux.vnet.ibm.com \
--to=preeti@linux.vnet.ibm.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=vatikaharlalka@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 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.