From: Alison Schofield <amsfield22@gmail.com>
To: Gargi Sharma <gs051095@gmail.com>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org
Subject: Re: [Outreachy kernel] [PATCH] staging: octeon: Removing multiple blank lines
Date: Tue, 13 Sep 2016 11:46:44 -0700 [thread overview]
Message-ID: <20160913184643.GA3351@d830.WORKGROUP> (raw)
In-Reply-To: <20160913160213.12708-1-gs051095@gmail.com>
On Tue, Sep 13, 2016 at 09:32:13PM +0530, Gargi Sharma wrote:
> Fixes the checkpatch issue Please don't use multiple blank lines.
Hi Gargi,
Just a couple of minor format comments, but you may as well v2 this
to get it looking it's best in the git history.
Typically the commit message is written in the imperative format.
That would be 'Remove' instead of 'Removing'. It's really not
necessary to become a grammar expert ;) just do a git pretty and
verify that your commit message is in the same style as the others
on the file you are changing:
git log --pretty=oneline --abbrev-commit <filename>
Within the changelog you can just cut/paste the checkpatch message,
as in: CHECK: Please don't use multiple blank lines. (Also tells
CHECK or WARNING)
> Fixes the checkpatch issue:
CHECK: Please don't use multiple blank lines
Really minor stuff, but it keeps the uniformity which is nice.
alisons
alisons
>
> Signed-off-by: Gargi Sharma <gs051095@gmail.com>
> ---
> drivers/staging/octeon/ethernet.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/staging/octeon/ethernet.c b/drivers/staging/octeon/ethernet.c
> index 0bd5c18..ec8e424 100644
> --- a/drivers/staging/octeon/ethernet.c
> +++ b/drivers/staging/octeon/ethernet.c
> @@ -686,7 +686,6 @@ static int cvm_oct_probe(struct platform_device *pdev)
> return -EINVAL;
> }
>
> -
> cvm_oct_configure_common_hw();
>
> cvmx_helper_initialize_packet_io_global();
> @@ -929,7 +928,6 @@ static int cvm_oct_remove(struct platform_device *pdev)
> }
> }
>
> -
> cvmx_pko_shutdown();
>
> cvmx_ipd_free_ptr();
> --
> 2.9.2
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20160913160213.12708-1-gs051095%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-09-13 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 16:02 [PATCH] staging: octeon: Removing multiple blank lines Gargi Sharma
2016-09-13 18:46 ` Alison Schofield [this message]
2016-09-13 20:50 ` [Outreachy kernel] " Gargi Sharma
2016-09-13 22:03 ` Alison Schofield
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=20160913184643.GA3351@d830.WORKGROUP \
--to=amsfield22@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gs051095@gmail.com \
--cc=outreachy-kernel@googlegroups.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.