All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Gargi Sharma <gs051095@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v2 1/2] staging: wlan-ng: use kernel preferred block commenting style
Date: Sat, 17 Sep 2016 23:25:43 +0200	[thread overview]
Message-ID: <20160917212543.GA5836@kroah.com> (raw)
In-Reply-To: <6b8722de3184861c05da59c3aad7cd6787079279.1474119677.git.gs051095@gmail.com>

On Sat, Sep 17, 2016 at 07:48:20PM +0530, Gargi Sharma wrote:
> Move the trailing markers to the next line to fix the checkpatch issue,
> trailing markers on the same line as the comment. Delete - in the multiline
> comments to follow the kernel coding style guide.
> 
> Signed-off-by: Gargi Sharma <gs051095@gmail.com>
> ---
>  drivers/staging/wlan-ng/hfa384x.h | 276 ++++++++++++++++++--------------------
>  1 file changed, 129 insertions(+), 147 deletions(-)

This patch does not apply to my tree, can you rebase both of these and
resend?

thanks,

greg k-h


  reply	other threads:[~2016-09-17 21:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 14:18 [PATCH v2 0/2] fix multiple coding style issues Gargi Sharma
2016-09-17 14:18 ` [PATCH v2 1/2] staging: wlan-ng: use kernel preferred block commenting style Gargi Sharma
2016-09-17 21:25   ` Greg KH [this message]
2016-09-17 14:18 ` [PATCH v2 2/2] staging: wlan-ng: change indentation for macros Gargi Sharma
2016-09-17 18:06 ` [PATCH v2 0/2] fix multiple coding style issues Greg KH
2016-09-17 18:12   ` Gargi Sharma
  -- strict thread matches above, loose matches on Subject: below --
2016-09-18 20:52 [PATCH v2 0/2] wlan-ng: " Gargi Sharma
2016-09-18 20:52 ` [PATCH v2 1/2] staging: wlan-ng: use kernel preferred block commenting style Gargi Sharma
2016-09-20 11:59   ` Greg KH

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=20160917212543.GA5836@kroah.com \
    --to=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.