From: Greg KH <gregkh@linuxfoundation.org>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>,
w.d.hubbs@gmail.com, chris@the-brannons.com, kirk@reisers.ca,
samuel.thibault@ens-lyon.org, speakup@linux-speakup.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 00/11] staging:speakup: Multiple Checkpatch issues.
Date: Wed, 22 Mar 2017 21:42:49 +0100 [thread overview]
Message-ID: <20170322204249.GA13164@kroah.com> (raw)
In-Reply-To: <6e75c652-f348-4592-a79d-4f290de9bea1@googlegroups.com>
On Wed, Mar 22, 2017 at 12:20:23PM -0700, Arushi Singhal wrote:
> On Tuesday, March 21, 2017 at 5:12:41 PM UTC+5:30, Arushi Singhal wrote:
>
> Improve readability by fixing multiple checkpatch.pl
> issues in speakup driver.
>
> Arushi Singhal (11):
> staging: speakup: Moved logical to previous line.
> staging: speakup: Remove multiple assignments
> staging: speakup: Simplify "NULL" comparisons
> staging: speakup: fixes braces {} should be used on all arms of this
> statement
> staging: speakup: Remove multiple assignments
> staging: speakup: Moved OR operator to previous line.
> staging: speakup: spaces preferred around operator
> staging: speakup: Removed Unnecessary parentheses.
> staging: speakup: Simplify the NULL comparisons
> staging: speakup: Match alignment with open parenthesis.
> staging: speakup: Fix alignment with parenthesis.
>
> drivers/staging/speakup/fakekey.c | 2 +-
> drivers/staging/speakup/kobjects.c | 2 +-
> drivers/staging/speakup/main.c | 110
> +++++++++++++++++--------------
> drivers/staging/speakup/selection.c | 4 +-
> drivers/staging/speakup/serialio.c | 2 +-
> drivers/staging/speakup/speakup.h | 12 ++--
> drivers/staging/speakup/speakup_acntpc.c | 8 +--
> drivers/staging/speakup/speakup_apollo.c | 2 +-
> drivers/staging/speakup/speakup_decext.c | 10 +--
> drivers/staging/speakup/speakup_decpc.c | 26 ++++----
> drivers/staging/speakup/speakup_dectlk.c | 6 +-
> drivers/staging/speakup/speakup_dtlk.c | 2 +-
> drivers/staging/speakup/speakup_keypc.c | 6 +-
> drivers/staging/speakup/speakup_ltlk.c | 2 +-
> drivers/staging/speakup/varhandlers.c | 18 ++---
> 15 files changed, 114 insertions(+), 98 deletions(-)
>
>
> Hi
> Any update on these patches?
One day? Please give us a chance, realize that it's normally a 2 week
timeframe to get a patch reviewed...
thanks,
greg k-h
prev parent reply other threads:[~2017-03-22 20:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 11:42 [RESEND PATCH 00/11] staging:speakup: Multiple Checkpatch issues Arushi Singhal
2017-03-21 11:42 ` [PATCH 01/11] staging: speakup: Moved logical to previous line Arushi Singhal
2017-03-21 11:42 ` [PATCH 02/11] staging: speakup: Remove multiple assignments Arushi Singhal
2017-03-23 13:18 ` Greg KH
2017-03-21 11:42 ` [PATCH 03/11] staging: speakup: Simplify "NULL" comparisons Arushi Singhal
2017-03-21 11:42 ` [PATCH 04/11] staging: speakup: fixes braces {} should be used on all arms of this statement Arushi Singhal
2017-03-21 11:42 ` [PATCH 05/11] staging: speakup: Remove multiple assignments Arushi Singhal
2017-03-23 13:18 ` Greg KH
2017-03-21 11:42 ` [PATCH 06/11] staging: speakup: Moved OR operator to previous line Arushi Singhal
2017-03-21 11:42 ` [PATCH 07/11] staging: speakup: spaces preferred around operator Arushi Singhal
2017-03-21 11:42 ` [PATCH 08/11] staging: speakup: Removed Unnecessary parentheses Arushi Singhal
2017-03-21 11:42 ` [PATCH 09/11] staging: speakup: Simplify the NULL comparisons Arushi Singhal
2017-03-23 13:19 ` Greg KH
2017-03-21 11:42 ` [PATCH 10/11] staging: speakup: Match alignment with open parenthesis Arushi Singhal
2017-03-21 11:42 ` [PATCH 11/11] staging: speakup: Fix alignment with parenthesis Arushi Singhal
2017-03-23 13:20 ` Greg KH
[not found] ` <6e75c652-f348-4592-a79d-4f290de9bea1@googlegroups.com>
2017-03-22 20:42 ` 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=20170322204249.GA13164@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arushisinghal19971997@gmail.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@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