All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chase Metzger <chasemetzger15@gmail.com>
Cc: Marcus Wolf <linux@Wolf-Entwicklungen.de>,
	Joseph Wright <rjosephwright@gmail.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Srishti Sharma <srishtishar@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] staging: pi433: pi433_if.c: coding style fixes
Date: Tue, 28 Nov 2017 14:10:21 +0100	[thread overview]
Message-ID: <20171128131021.GA32275@kroah.com> (raw)
In-Reply-To: <cover.1510790802.git.chasemetzger15@gmail.com>

On Wed, Nov 15, 2017 at 04:35:47PM -0800, Chase Metzger wrote:
> Fixes some of the coding style violations to comply with the kernel
> coding style.
> 
> Chase Metzger (6):
>   staging: pi433: pi433_if.c: fix opening curly brace coding style
>     issues
>   staging: pi433: pi433_if.c: fix else if/else statements coding style
>     issues
>   staging: pi433: pi433_if.c: fix trailing statement coding style issues
>   staging: pi433: pi433_if.c: fix space prohibited coding style issues
>   staging: pi433: pi433_if.c: fix space(s) required coding style issues
>   staging: pi433: pi433_if.c: use tabs instead of spaces
> 
>  drivers/staging/pi433/pi433_if.c | 203 +++++++++++++++++----------------------
>  1 file changed, 87 insertions(+), 116 deletions(-)

Please rebase and resend this series based on the review comments.

thanks,

greg k-h

      parent reply	other threads:[~2017-11-28 13:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16  0:35 [PATCH 0/6] staging: pi433: pi433_if.c: coding style fixes Chase Metzger
2017-11-16  0:35 ` [PATCH 1/6] staging: pi433: pi433_if.c: fix opening curly brace coding style issues Chase Metzger
2017-11-28 13:08   ` Greg KH
2017-11-16  0:35 ` [PATCH 2/6] staging: pi433: pi433_if.c: fix else if/else statements " Chase Metzger
2017-11-16  0:35 ` [PATCH 3/6] staging: pi433: pi433_if.c: fix trailing statement " Chase Metzger
2017-11-16  0:35 ` [PATCH 4/6] staging: pi433: pi433_if.c: fix space prohibited " Chase Metzger
2017-11-28 13:09   ` Greg KH
2017-11-16  0:35 ` [PATCH 5/6] staging: pi433: pi433_if.c: fix space(s) required " Chase Metzger
2017-11-16  0:35 ` [PATCH 6/6] staging: pi433: pi433_if.c: use tabs instead of spaces Chase Metzger
2017-11-28 13:10 ` Greg KH [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=20171128131021.GA32275@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chasemetzger15@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@Wolf-Entwicklungen.de \
    --cc=rjosephwright@gmail.com \
    --cc=srishtishar@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.