All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gargi Sharma <gs051095@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: outreachy-kernel@googlegroups.com, Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [Outreachy kernel] [PATCH] staging: wlan-ng: add blank line after declaration
Date: Thu, 16 Feb 2017 16:29:38 +0530	[thread overview]
Message-ID: <CAOCi2DGNp1U2kQKV_0GUrF29k0-bzmWbzuU9Q95CLxr7yz7XvQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702161117310.3091@hadrien>

[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]

On Thu, Feb 16, 2017 at 3:49 PM, Julia Lawall <julia.lawall@lip6.fr> wrote:
>
>
>
> On Thu, 16 Feb 2017, Gargi Sharma wrote:
>
> > add blank line after struct declaration to fix the checkpatch issue, add
> > blank line after declarations.
>
> This does not look right.  The code before and the code after are all
> declarations.  I think that checkpatch is misinterpreting the code.  This

Okay, will revert this commit.

Thanks,
Gargi

> warning is normally targeted at local variables in functions.
>
> The code is fine as is.
>
> julia
>
> > Signed-off-by: Gargi Sharma <gs051095@gmail.com>
> > ---
> >  drivers/staging/wlan-ng/hfa384x.h | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/staging/wlan-ng/hfa384x.h
b/drivers/staging/wlan-ng/hfa384x.h
> > index 5f1851c..f199847 100644
> > --- a/drivers/staging/wlan-ng/hfa384x.h
> > +++ b/drivers/staging/wlan-ng/hfa384x.h
> > @@ -1175,6 +1175,7 @@ struct hfa384x_usbctlx {
> >       enum ctlx_state state;  /* Tracks running state */
> >
> >       struct completion done;
> > +
> >       volatile int reapable;  /* Food for the reaper task */
> >
> >       ctlx_cmdcb_t cmdcb;     /* Async command callback */
> > --
> > 2.7.4
> >
> > --
> > 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/1487239937-26115-1-git-send-
email-gs051095%40gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
> >

[-- Attachment #2: Type: text/html, Size: 2738 bytes --]

  reply	other threads:[~2017-02-16 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 10:12 [PATCH] staging: wlan-ng: add blank line after declaration Gargi Sharma
2017-02-16 10:19 ` [Outreachy kernel] " Julia Lawall
2017-02-16 10:59   ` Gargi Sharma [this message]
2017-02-16 16:56 Gargi Sharma
2017-02-16 19:41 ` [Outreachy kernel] " Julia Lawall

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=CAOCi2DGNp1U2kQKV_0GUrF29k0-bzmWbzuU9Q95CLxr7yz7XvQ@mail.gmail.com \
    --to=gs051095@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@lip6.fr \
    --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.