From: Jes Sorensen <jes.sorensen@gmail.com>
To: Gamze POLAT <gamzepolat94@gmail.com>, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: rtl8712: Add blank line
Date: Fri, 20 Feb 2015 14:37:03 -0500 [thread overview]
Message-ID: <54E78CDF.7000601@gmail.com> (raw)
In-Reply-To: <1424458703-6100-1-git-send-email-gamzepolat94@gmail.com>
On 02/20/15 13:58, Gamze POLAT wrote:
> WARNING: "Missing a blank line after declarations"
> That was found by running checkpatch.
>
> Signed-off-by: Gamze POLAT <gamzepolat94@gmail.com>
> ---
> drivers/staging/rtl8712/drv_types.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/staging/rtl8712/drv_types.h b/drivers/staging/rtl8712/drv_types.h
> index e62543d..a775f8d 100644
> --- a/drivers/staging/rtl8712/drv_types.h
> +++ b/drivers/staging/rtl8712/drv_types.h
> @@ -129,6 +129,7 @@ struct dvobj_priv {
> struct _adapter *padapter;
> u32 nr_endpoint;
> u8 ishighspeed;
> +
> uint (*inirp_init)(struct _adapter *adapter);
> uint (*inirp_deinit)(struct _adapter *adapter);
> struct usb_device *pusbdev;
> @@ -166,6 +167,7 @@ struct _adapter {
> pid_t evtThread;
> struct task_struct *xmitThread;
> pid_t recvThread;
> +
> uint (*dvobj_init)(struct _adapter *adapter);
> void (*dvobj_deinit)(struct _adapter *adapter);
> struct net_device *pnetdev;
>
This patch is actually wrong - I think checkpatch is confused here by
the declaration of function pointers, treating them like functions.
I do spot a whitespace issue that needs fixing in your patch, but the
blank lines added shouldn't be added.
Cheers,
Jes
prev parent reply other threads:[~2015-02-20 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 18:58 [PATCH] staging: rtl8712: Add blank line Gamze POLAT
2015-02-20 19:37 ` Jes Sorensen [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=54E78CDF.7000601@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=gamzepolat94@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.