All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Scott Matheina <scott@matheina.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	Ivan Safonov <insafonov@gmail.com>,
	Anchal Jain <anchalj109@gmail.com>,
	Kyle Kuffermann <kyle.kuffermann@gmail.com>,
	Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
	Luca Ceresoli <luca@lucaceresoli.net>
Subject: Re: [PATCH 0/2] Fixes coding style
Date: Thu, 5 Jan 2017 18:19:25 +0100	[thread overview]
Message-ID: <20170105171925.GA21734@kroah.com> (raw)
In-Reply-To: <1483578661-7790-1-git-send-email-scott@matheina.com>

On Wed, Jan 04, 2017 at 07:10:39PM -0600, Scott Matheina wrote:
> The patch series addresses some coding style issues contained within the file.
> 
> Scott Matheina (2):
>   drivers/staging/rtl8188eu/core/rtw_ap.c un-necessary parenthesis
>   drivers/staging/rtl8188eu/core/rtw_ap.c Alignment should match open
>     parenthesis
> 
>  drivers/staging/rtl8188eu/core/rtw_ap.c | 144 ++++++++++++++++----------------
>  1 file changed, 71 insertions(+), 73 deletions(-)

Your subject line here could use some work, it needs to say where you
are doing the work.  For example it could have said:
	[PATCH 0/2] staging: rtl8188eu: coding style fixes

Or better yet, no 0/2 email at all, a two patch series doesn't need it.

thanks,

greg k-h

      parent reply	other threads:[~2017-01-05 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05  1:10 [PATCH 0/2] Fixes coding style Scott Matheina
2017-01-05  1:10 ` [PATCH 1/2] drivers/staging/rtl8188eu/core/rtw_ap.c un-necessary parenthesis Scott Matheina
2017-01-05 17:20   ` Greg Kroah-Hartman
2017-01-05  1:10 ` [PATCH 2/2] drivers/staging/rtl8188eu/core/rtw_ap.c Alignment should match open parenthesis Scott Matheina
2017-01-05 17:19 ` Greg Kroah-Hartman [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=20170105171925.GA21734@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=anchalj109@gmail.com \
    --cc=bhaktipriya96@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=insafonov@gmail.com \
    --cc=kyle.kuffermann@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca@lucaceresoli.net \
    --cc=scott@matheina.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.