From: Greg KH <gregkh@linuxfoundation.org>
To: Juliana Rodrigues <juliana.orod@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2 2/6] staging: rtl8188eu: usb_halinit.c: fixed comment blocks
Date: Mon, 21 Mar 2016 16:55:40 -0400 [thread overview]
Message-ID: <20160321205540.GC25708@kroah.com> (raw)
In-Reply-To: <f5ff61beecc688c4a7482b38231ffd3b7f6ecf27.1458043217.git.juliana.orod@gmail.com>
On Tue, Mar 15, 2016 at 09:03:52AM -0300, Juliana Rodrigues wrote:
> This patch fixes checkpatch warnings related to
> malformed comments and comments over 80 characters limit.
> It also removes some clearly unnecessary/old ones
> and fixes minor check issues.
Again, only do one thing per patch. I'll stop reviewing here and let
you respin this series...
thanks,
greg k-h
next prev parent reply other threads:[~2016-03-21 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 12:02 [PATCH v2 0/6] staging: rtl8188eu: usb_halinit.c: fixes multiple errors and warnings Juliana Rodrigues
2016-03-15 12:03 ` [PATCH v2 1/6] staging: rtl8188eu: usb_halinit.c: fixed multiple warnings Juliana Rodrigues
2016-03-21 20:55 ` [Outreachy kernel] " Greg KH
2016-03-15 12:03 ` [PATCH v2 2/6] staging: rtl8188eu: usb_halinit.c: fixed comment blocks Juliana Rodrigues
2016-03-21 20:55 ` Greg KH [this message]
2016-03-15 12:04 ` [PATCH v2 3/6] staging: rtl8188eu: usb_halinit.c: fixes comparison warning Juliana Rodrigues
2016-03-15 12:04 ` [PATCH v2 4/6] staging: rtl8188eu: usb_halinit.c: remove unnecessary braces Juliana Rodrigues
2016-03-15 12:05 ` [PATCH v2 5/6] staging: rtl8188eu: usb_halinit.c: removes unnecessary parentheses Juliana Rodrigues
2016-03-15 12:05 ` [PATCH v2 6/6] staging: rtl8188eu: usb_halinit.c: removes else after return Juliana Rodrigues
2016-03-21 20:54 ` [Outreachy kernel] [PATCH v2 0/6] staging: rtl8188eu: usb_halinit.c: fixes multiple errors and warnings 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=20160321205540.GC25708@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=juliana.orod@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.