From: Alison Schofield <amsfield22@gmail.com>
To: Tamara Diaconita <diaconitatamara@gmail.com>
Cc: aditya.shankar@microchip.com, ganesh.krishna@microchip.com,
gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com,
Tamara Diaconita <diaconita.tamara@gmail.com>
Subject: Re: [Outreachy kernel] [PATCH 3/3] staging: wilc1000: wilc_spi: Add blank line
Date: Wed, 8 Mar 2017 12:27:45 -0800 [thread overview]
Message-ID: <20170308202744.GC2787@d830.WORKGROUP> (raw)
In-Reply-To: <20170308170652.3996-1-diaconita.tamara@gmail.com>
On Wed, Mar 08, 2017 at 07:06:52PM +0200, Tamara Diaconita wrote:
> Add a blank line after a function.
>
> Fix the checkpath.pl issue:
^^^^checkpatch
Hi Tamara,
This one looks good, but since you're going to rev the
patchset for the others, I'm going to be picky and ask you to
update this for the checkpatch spelling and for the subject line.
I did a gitpretty (alias gitpretty='git log --pretty=oneline
--abbrev-commit') to see what is customary for this file.
Just the driver name is customary. I see that one submitter
before you, added the filename also, but let's not continue
that trend ;)
Dropping the .c filename from the subject line applies to
all patches in the set.
Thanks,
alisons
> CHECK: Please use a blank line after function/struct/union.
>
> Signed-off-by: Tamara Diaconita <diaconita.tamara@gmail.com>
> ---
> drivers/staging/wilc1000/wilc_spi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/staging/wilc1000/wilc_spi.c b/drivers/staging/wilc1000/wilc_spi.c
> index 4a4b8c3..82d162d 100644
> --- a/drivers/staging/wilc1000/wilc_spi.c
> +++ b/drivers/staging/wilc1000/wilc_spi.c
> @@ -1146,6 +1146,7 @@ static int wilc_spi_sync_ext(struct wilc *wilc, int nint)
>
> return 1;
> }
> +
> /********************************************
> *
> * Global spi HIF function table
> --
> 2.9.3
>
> --
> 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/20170308170652.3996-1-diaconita.tamara%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2017-03-08 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 17:06 [PATCH 3/3] staging: wilc1000: wilc_spi: Add blank line Tamara Diaconita
2017-03-08 20:27 ` Alison Schofield [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=20170308202744.GC2787@d830.WORKGROUP \
--to=amsfield22@gmail.com \
--cc=aditya.shankar@microchip.com \
--cc=diaconita.tamara@gmail.com \
--cc=diaconitatamara@gmail.com \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--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.