public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Walt Feasel <waltfeasel@gmail.com>
Cc: w.d.hubbs@gmail.com, devel@driverdev.osuosl.org, kirk@reisers.ca,
	speakup@linux-speakup.org, linux-kernel@vger.kernel.org,
	samuel.thibault@ens-lyon.org, chris@the-brannons.com
Subject: Re: [PATCH v2 0/6] staging: speakup: speakup_soft.c checkpatch modifications
Date: Wed, 23 Nov 2016 10:09:05 +0100	[thread overview]
Message-ID: <20161123090905.GA31482@kroah.com> (raw)
In-Reply-To: <1479741565-19419-1-git-send-email-waltfeasel@gmail.com>

On Mon, Nov 21, 2016 at 10:19:19AM -0500, Walt Feasel wrote:
> Make Linux kernel style modifications for speak_soft.c to include:
> 
> Space around operator
> Logical continuation
> Multiple blank lines
> Blank line after {
> comment modifications
> Align parenthesis

Ok, now that you have a bunch of cleanup patches accepted, why not work
on some "real" code changes?  There's no need to fix all of the coding
style issues in drivers/staging/ at once, leave some for other people to
learn on :)

thanks,

greg k-h

  parent reply	other threads:[~2016-11-23  9:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 15:19 [PATCH v2 0/6] staging: speakup: speakup_soft.c checkpatch modifications Walt Feasel
2016-11-21 15:19 ` [PATCH v2 1/6] staging: speakup: speakup_soft.c Space around operator Walt Feasel
2016-11-21 15:19 ` [PATCH v2 2/6] staging: speakup: speakup_soft.c Logical continuation Walt Feasel
2016-11-21 15:19 ` [PATCH v2 3/6] staging: speakup: speakup_soft.c Multiple blank lines Walt Feasel
2016-11-21 15:19 ` [PATCH v2 4/6] staging: speakup: speakup_soft.c Blank line after { Walt Feasel
2016-11-21 15:19 ` [PATCH v2 5/6] staging: speakup: speakup_soft.c comment modifications Walt Feasel
2016-11-21 15:19 ` [PATCH v2 6/6] staging: speakup: speakup_soft.c Align parenthesis Walt Feasel
2016-11-23  9:09 ` Greg KH [this message]
     [not found]   ` <CACfmeC=-NKgX4QKF0Btj6OTvOxSjZgcoQ4BrNLq5NEpPSZ+1Ww@mail.gmail.com>
2016-11-23 15:56     ` [PATCH v2 0/6] staging: speakup: speakup_soft.c checkpatch modifications Greg KH
2016-11-23 16:24       ` Walt Feasel

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=20161123090905.GA31482@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris@the-brannons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@gmail.com \
    --cc=waltfeasel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox